Re: Listen / Notify - what to do when the queue is full
Joachim Wieland <joe@mcknight.de>
From: Joachim Wieland <joe@mcknight.de>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "Florian G. Pflug" <fgp@phlo.org>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2009-11-20T08:34:16Z
Lists: pgsql-hackers
On Fri, Nov 20, 2009 at 7:51 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: >> Note that we don't preserve notifications when the database restarts. >> But 2PC can cope with restarts. How would that fit together? > > The notifications are written to the state file at prepare. They can be > recovered from there and written to the queue again at server start (see > twophase_rmgr.c). Okay, but which of the backends would then leave its pointer at that place in the queue upon restart? This is also an issue for the non-restart case, what if you prepare the transaction in one backend and commit in the other? Joachim