On Mon, Jan 9, 2012 at 5:58 AM, Chris Angelico <rosuav@xxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
