Re: Do "after update" trigger block the current transaction?

From: Clemens Eisserer <linuxhippy(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Do "after update" trigger block the current transaction?
Date: 2013-03-26 14:27:26
Message-ID: CAFvQSYRYDVn2A+CZWA1DjEMHJDSyZggk1nuZHu4WbiofrmONqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2013-03-26 15:55:40 Why does Postgres allow duplicate (FK) constraints
Previous Message Richard Huxton 2013-03-26 14:00:26 Re: Do "after update" trigger block the current transaction?