Re: Do "after update" trigger block the current transaction? - Mailing list pgsql-general

From Clemens Eisserer
Subject Re: Do "after update" trigger block the current transaction?
Date
Msg-id CAFvQSYRYDVn2A+CZWA1DjEMHJDSyZggk1nuZHu4WbiofrmONqA@mail.gmail.com
Whole thread Raw
In response to Re: Do "after update" trigger block the current transaction?  (Richard Huxton <dev@archonet.com>)
List pgsql-general
Hi Richard,

> Might be worth looking at PgQ - a queueing system underlying Londiste. That
> would handle tracking the changes in PostgreSQL leaving you to just handle
> the MySQL end. Timestamps will do the job as long as you are careful to
> allow enough slack to deal with clock updates.

Thanks a lot, PgQ seems to be exactly what I was looking for :-)
Another solution that came to my mind is notifying the "replication
daemon" using NOTIFY/LISTEN.

Thanks again, Clemens


pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Do "after update" trigger block the current transaction?
Next
From: Thomas Kellerer
Date:
Subject: Why does Postgres allow duplicate (FK) constraints