| From: | Joachim Wieland <joe(at)mcknight(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "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: | 2010-01-20 22:39:01 |
| Message-ID: | dc7b844e1001201439m3c45417epd1c3f44fe42ea50a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 20, 2010 at 11:08 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>> Yes. That is the case with the existing implementation as well, no?
>> We don't consider sending notifies until transaction end, so anything
>> that commits during the xact in which you UNLISTEN will get dropped.
>
> Only if the transaction containing UNLISTEN commits. Are you saying it
> would also be OK to drop NOTIFYs if a backend's UNLISTEN transaction
> aborts?
If the backend's UNLISTEN transaction aborts, then it has never
executed UNLISTEN...
So it will continue to get notifications (if it has executed a LISTEN before).
Joachim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-20 22:40:26 | Re: Listen / Notify - what to do when the queue is full |
| Previous Message | Kevin Grittner | 2010-01-20 22:16:56 | Serializable implementation milestone: table SIREAD locks without correct lifespan |