| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | 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:33:11 |
| Message-ID: | 20061204143311.GC28324@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
What will happen when the ring is full? NOTIFY blocks?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-12-04 14:41:02 | Re: Notify enhancement |
| Previous Message | Teodor Sigaev | 2006-12-04 14:10:25 | Bundle of patches |