| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Listen / Notify - what to do when the queue is full |
| Date: | 2009-11-20 08:34:16 |
| Message-ID: | dc7b844e0911200034u5c6b355eua85185b43018d420@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 20, 2009 at 7:51 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pye | 2009-11-20 08:59:56 | Re: Python 3.1 support |
| Previous Message | Peter Eisentraut | 2009-11-20 08:30:07 | Re: enable-thread-safety defaults? |