Re: Listen / Notify - what to do when the queue is full

From: Joachim Wieland <joe(at)mcknight(dot)de>
To: "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Listen / Notify - what to do when the queue is full
Date: 2009-11-19 13:23:57
Message-ID: dc7b844e0911190523t5b055bd5h6e45f63c9dd7fd76@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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).

Joachim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2009-11-19 13:29:05 Question about ECPGset_noind_null() and ECPGis_noind_null()
Previous Message Joachim Wieland 2009-11-19 13:16:28 Re: Listen / Notify - what to do when the queue is full