Re: Notify enhancement - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Notify enhancement
Date
Msg-id 4574337E.9020603@dunslane.net
Whole thread Raw
In response to Re: Notify enhancement  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Notify enhancement  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Notify enhancement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Alvaro Herrera wrote:
> Andrew Dunstan wrote:
>
>   
>> Ok. But I think the buffer size as a whole needs to be fixed, no? And if 
>> so, we probably need some limit on message size to prevent "NOTIFY 
>> some_event 'a really long string'; " from filling up the buffer in one hit.
>>
>> I'm also trying to figure out what a reasonable default buffer size will 
>> be. Thinking of the needs for which I will be providing (one listener, 
>> small names/payloads), 256Kb or 512Kb would be ample, possibly even 
>> excessive. But other users might have bigger needs.
>>     
>
> Make it configurable via GUC.
>   

That was my intention. The question was what the default should be.

> What will happen when the ring is full?  NOTIFY blocks?
>
>   
An error, I think, don't you? Blocking seems totally unacceptable.

cheers

andrew


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Notify enhancement
Next
From: Alvaro Herrera
Date:
Subject: Re: Notify enhancement