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

Поиск
Список
Период
Сортировка
От Clemens Eisserer
Тема Re: Do "after update" trigger block the current transaction?
Дата
Msg-id CAFvQSYRYDVn2A+CZWA1DjEMHJDSyZggk1nuZHu4WbiofrmONqA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Do "after update" trigger block the current transaction?  (Richard Huxton <dev@archonet.com>)
Список 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 по дате отправления:

Предыдущее
От: Richard Huxton
Дата:
Сообщение: Re: Do "after update" trigger block the current transaction?
Следующее
От: Thomas Kellerer
Дата:
Сообщение: Why does Postgres allow duplicate (FK) constraints