Re: Feature request: binary NOTIFY
От | Tom Lane |
---|---|
Тема | Re: Feature request: binary NOTIFY |
Дата | |
Msg-id | 381.1568729401@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Feature request: binary NOTIFY (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: Feature request: binary NOTIFY
Re: Feature request: binary NOTIFY |
Список | pgsql-hackers |
Pavel Stehule <pavel.stehule@gmail.com> writes: > út 17. 9. 2019 v 10:01 odesílatel Mitar <mmitar@gmail.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. regards, tom lane
В списке pgsql-hackers по дате отправления: