| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | jedwards(at)fastmail(dot)com |
| Subject: | BUG #15558: NOTIFY max channel length is undocumented |
| Date: | 2018-12-19 00:28:35 |
| Message-ID: | 15558-996f38aafa654215@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15558
Logged by: Andy Edwards
Email address: jedwards(at)fastmail(dot)com
PostgreSQL version: 11.1
Operating system: (irrelevant)
Description:
After debugging why notifications weren't getting delivered, I discovered
the following:
# LISTEN "pg/tables/TagNotificationTriggers/tag/_org/1/JSON
Test/battery/1/lifetimeWh";
NOTICE: identifier "pg/tables/TagNotificationTriggers/tag/_org/1/JSON
Test/battery/1/lifetimeWh" will be truncated to
"pg/tables/TagNotificationTriggers/tag/_org/1/JSON Test/battery/"
I haven't seen a mention of this channel length limit in any version of the
documentation for NOTIFY. I wish it were in the documentation, because then
I would have found out about this limit before deciding to use Postgres
notifications, and chosen to use Redis notifications from the beginning.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-12-19 00:44:42 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |
| Previous Message | Luis Carril | 2018-12-18 13:41:04 | Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction |