| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Notify enhancement |
| Date: | 2006-12-04 14:41:02 |
| Message-ID: | 4574337E.9020603@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-12-04 14:44:39 | Re: Notify enhancement |
| Previous Message | Alvaro Herrera | 2006-12-04 14:33:11 | Re: Notify enhancement |