On Thu, 22 Nov 2012, Achilleas Mantzios wrote:

> 
> Thank you for your answer.
> 
> 
> 
> It is this case 3) that we must deal with. At the vessel side (we don't care for the Office for the moment)
> 
> we want to eliminate bounce back while reading SQL from the master, therefore we would like to allow
> 
> triggers operating freely as by default on all occasions except in the program which reads and executes
> 
> SQL generated and sent by the Office.

Can't you just make the dbmirror log trigger a 'normal' trigger that is 
enabled everywhere.  You would then modify 
dbmirror.pl to connect with session_replication_role='replica'.  The 
dbmirror triggers won't fire on the replica in response to data being 
sent from dbmirror so there will be no rows in the pendingData table to 
bounce back.

The application on the ships would connect with out touching 
session_replication_role so the dbmirror trigger would fire for any inserts 
they do leaving you rows in pendingData to pull elsewhere.

This is basically how slony works, except slony installs a deny access 
trigger on the replica tables to prevent writes.


Steve