From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Mitar <mmitar(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature request: binary NOTIFY |
Date: | 2019-09-17 15:07:43 |
Message-ID: | CAFj8pRCyMQJMzPyOw=odH2MpQup7MHRb0U5OU1yCcCuJmU3zgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
út 17. 9. 2019 v 16:10 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > út 17. 9. 2019 v 10:01 odesílatel Mitar <mmitar(at)gmail(dot)com> napsal:
> >> I might have missed prior discussions about this, but I wonder if it
> >> would be possible to support binary payloads for NOTIFY/LISTEN? Again
> >> and again I find it very limiting with just text (have to base64
> >> encode data, or convert it to JSON).
>
> > I think so is not any problem to pass binary data already.
>
> Yeah it is ... the internal async-queue data structure assumes
> null-terminated strings. What's a lot worse, so does the
> wire protocol's NotificationResponse message, as well as every
> existing client that can read it. (For instance, libpq's exposed
> API for notify messages hands back the payload as a null-terminated
> string.) I don't think this is going to happen.
>
ok, thank you for correction.
Regards
Pavel
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2019-09-17 15:15:42 | Re: patch: psql - enforce constant width of last column |
Previous Message | Ahsan Hadi | 2019-09-17 15:06:09 | Re: patch: psql - enforce constant width of last column |