On 26/03/13 08:52, Clemens Eisserer wrote:
Hi, We are currently evaluating the feasibility of executing long-running scripts written in shell-script (plsh) called by triggers (after update/insert) to synchronize two databases. Will triggers (after update specifically) cause the execution of SQL-commands to pause until the trigger-function has returned (at statement execution time or commit)?
The trigger will block. If it didn't then it couldn't abort the transaction if it needed to.
The other possible approach would be to use polling on some trigger-updated timestamp-column, which is not pretty but should be fairly simple.
Why not use one of the established trigger-based replication solutions? -- Richard Huxton Archonet Ltd -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
