On May 19, 2008, at 6:53 PM, Tom Lane wrote:
Another response I've heard is "but I don't want to make
inside-the-database changes, I want to propagate the state to
someplace
external". Of course that's completely broken too, because there is
*absolutely no way* you will ever make such changes atomic with the
inside-the-database transaction commit. We discourage people from
making triggers cause outside-the-database side effects already ---
it's not going to be better to do it in an "on commit" trigger.
Isn't this close to what NOTIFY is? An on-commit trigger that
causes only outside-the-database effects.
Cheers,
Steve
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
