Re: Listen / Notify - what to do when the queue is full
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Joachim Wieland <joe@mcknight.de>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Jeff Davis <pgsql@j-davis.com>, Tom Lane <tgl@sss.pgh.pa.us>, Greg Smith <greg@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, "Florian G. Pflug" <fgp@phlo.org>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org, Arnaud Betremieux <arnaud.betremieux@keyconsulting.fr>
Date: 2010-02-14T17:41:39Z
Lists: pgsql-hackers
On Sun, 2010-02-14 at 17:22 +0100, Joachim Wieland wrote: > > * There is no mention of what to do with pg_notify at checkpoint. > Look > > at how pg_subtrans handles this. Should pg_notify do the same? > > Actually we don't care... We even hope that the pg_notify pages are > not flushed at all. Notifications don't survive a server restart > anyway and upon restart we just delete whatever is in the directory. Suspected that was true, just checking it was commented somewhere. -- Simon Riggs www.2ndQuadrant.com