Do "after update" trigger block the current transaction?

From: Clemens Eisserer <linuxhippy(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Do "after update" trigger block the current transaction?
Date: 2013-03-26 08:52:40
Message-ID: CAFvQSYRVn3Ad76XGFPTJO266-nVf3qRQNDNuvQEtKFxATMdz-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 other possible approach would be to use polling on some
trigger-updated timestamp-column, which is not pretty but should be
fairly simple.

Thank you in advance, Clemens

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2013-03-26 08:59:19 Re: Acess Oracle with dbi-link (PostgreSQL) Error Compile
Previous Message Bartosz Dmytrak 2013-03-26 08:35:19 effective_io_concurrency on Windows