Re: Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts

Поиск
Список
Период
Сортировка
От Marko Kreen
Тема Re: Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts
Дата
Msg-id CACMqXC+HS5nKZzSDmEC0pLdZ-kXwHCr9OeXAUCVZiG7XZAehaA@mail.gmail.com
обсуждение исходный текст
Ответ на Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts  (Chris Angelico <rosuav@gmail.com>)
Ответы Re: Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts  (Chris Angelico <rosuav@gmail.com>)
Список pgsql-general
On Mon, Jan 9, 2012 at 5:58 AM, Chris Angelico <rosuav@gmail.com> wrote:
> http://wiki.postgresql.org/wiki/PGQ_Tutorial
>
> PGQ looks promising, but I can't afford the risk of losing calls in
> the event that there are no workers to process them (the correct
> action is for them simply to languish in the database until one is
> started up).

PGQ does not lose events - after consumer registers
on the queue it is guaranteed to see all events.

So it's a matter of registering your consumers
before anything interesting happens in database.
The actual consumers do not need to be running
at that moment.

--
marko

В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: pg_dump -s dumps data?!
Следующее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: pg_dump -s dumps data?!