From: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Listen / Notify - what to do when the queue is full |
Date: | 2009-11-19 16:18:48 |
Message-ID: | 20091119171848.287225f8@iridium.wars-nicht.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 19 Nov 2009 14:23:57 +0100 Joachim Wieland wrote:
> On Thu, Nov 19, 2009 at 1:51 PM, Andreas 'ads' Scherbaum
> <adsmail(at)wars-nicht(dot)de> wrote:
> > And in addition i don't like the idea of having the sender sitting
> > around until there's room for more messages in the queue, because some
> > very old backends didn't remove the stuff from the same.
>
> The only valid reason why a backend has not processed the
> notifications in the queue
> must be a backend that is still in a transaction since then (and has
> executed LISTEN
> some time before).
Yes, i know. The same backend is probably causing more trouble
anyway (blocking vacuum, xid wraparound, ...).
--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2009-11-19 16:37:50 | Re: Listen / Notify - what to do when the queue is full |
Previous Message | Tom Lane | 2009-11-19 16:17:16 | Re: Listen / Notify - what to do when the queue is full |