| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | sulfinu(at)gmail(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Size limit for NOTIFY payload |
| Date: | 2024-12-20 14:16:30 |
| Message-ID: | CAKAnmmLX=FzrWSzN1eB6Se54sWUm7J44h+3WvbxjZM5rR+DvxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Dec 20, 2024 at 5:53 AM <sulfinu(at)gmail(dot)com> wrote:
> Well, as I said, that's a *text* value with a *byte* limit. The
> documentation should definitely mention something like *"with the default
> database encoding"*.
>
I'm not sure why you think adding such wordage is needed. Bytes is bytes.
Your application should be checking the number of bytes in the string sent
to NOTIFY.
On a related note, if you find yourself approaching the payload limits, you
might want to rethink the way you are using LISTEN/NOTIFY.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2024-12-21 03:32:53 | restart-footnote-numbering-in-each-sect1 |
| Previous Message | sulfinu | 2024-12-19 09:00:18 | Re: Size limit for NOTIFY payload |