Hi!
On Wed, Sep 18, 2019 at 9:22 PM Tom Lane wrote:
> [ shrug... ] We can put that on the list of things we might want
> to do if the wire protocol ever gets changed. I urgently recommend
> not holding your breath.
What is the process to add it to the list?
And yes, I will not expect it soon.
Mitar writes:
> What about adding NOTIFYB and LISTENB commands? And
> NotificationBinaryResponse? For binary?
[ shrug... ] We can put that on the list of things we might want
to do if the wire protocol ever gets changed. I urgently recommend
not holding your breath.
reg
Hi!
On Tue, Sep 17, 2019 at 7:10 AM Tom Lane wrote:
> 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, lib
út 17. 9. 2019 v 16:10 odesílatel Tom Lane napsal:
> Pavel Stehule writes:
> > út 17. 9. 2019 v 10:01 odesílatel Mitar 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 fi
Pavel Stehule writes:
> út 17. 9. 2019 v 10:01 odesílatel Mitar 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 da
Hi
út 17. 9. 2019 v 10:01 odesílatel Mitar napsal:
> Hi!
>
> 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 i
Hi!
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).
Mitar
--
http://mitar.tnode.com/
https://twitter.