Re: Listen / Notify - what to do when the queue is full - Mailing list pgsql-hackers

From Joachim Wieland
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id dc7b844e0911200034u5c6b355eua85185b43018d420@mail.gmail.com
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Listen / Notify - what to do when the queue is full
List 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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: enable-thread-safety defaults?
Next
From: James Pye
Date:
Subject: Re: Python 3.1 support