| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Listen / Notify rewrite |
| Date: | 2009-11-12 03:45:23 |
| Message-ID: | 4AFB84D3.3040109@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> 2. The payload parameter is optional. A notifying client can either call
>> "NOTIFY foo;" or "NOTIFY foo 'payload';". The length of the payload is
>> currently limited to 128 characters... Not sure if we should allow longer
>> payload strings...
>
> Might be a good idea to make the max the same as the max length for
> prepared transaction GUIDs? Not sure anyone would be shipping those
> around, but it's a pre-existing limit of about the same size.
>
I don't see any reason to impose such a small limit on payload size. Surely
some limit must exist, but 128 characters seems awfully small. I already have
at few places in mind that would require more bytes.
Why not 8K, 64K, 256K, 1M or even more? Is there some other factor in play
forcing this limitation?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-11-12 04:31:23 | Re: write ahead logging in standby (streaming replication) |
| Previous Message | Tom Lane | 2009-11-12 03:43:06 | Re: Listen / Notify rewrite |