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

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Chris Angelico <rosuav(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts
Date: 2012-01-30 17:12:06
Message-ID: CACMqXC+HS5nKZzSDmEC0pLdZ-kXwHCr9OeXAUCVZiG7XZAehaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 9, 2012 at 5:58 AM, Chris Angelico <rosuav(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2012-01-30 17:23:15 Re: pg_dump -s dumps data?!
Previous Message Adrian Klaver 2012-01-30 17:03:47 Re: pg_dump -s dumps data?!