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

From Andrew Chernow
Subject Re: Listen / Notify - what to do when the queue is full
Date
Msg-id 4B04BC3E.3070004@esilo.com
Whole thread Raw
In response to Re: Listen / Notify - what to do when the queue is full  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Listen / Notify - what to do when the queue is full
List pgsql-hackers
Tom Lane wrote:
> Andrew Chernow <ac@esilo.com> writes:
>> I mentioned this up thread.  I completely agree that overflow behavior should be 
>> tunable.
> 
> There is only one correct overflow behavior.
> 

I count three.

1. wait
2. error
3. skip

#1 and #2 are very similar to a file system.  If FS buffers are full on write, 
it makes you wait.  In non-blocking mode, it throws an EAGAIN error.  IMHO those 
two behaviors are totally acceptable for handling notify overflow.  #3 is pretty 
weak but I *think* there are uses for it.

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Euler Taveira de Oliveira
Date:
Subject: Re: ProcessUtility_hook
Next
From: Tom Lane
Date:
Subject: Re: "Not safe to send CSV data" message