From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Mitar <mmitar(at)gmail(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature request: binary NOTIFY |
Date: | 2019-09-17 08:22:35 |
Message-ID: | CAFj8pRC24Sy7xusVCKdvMJsj=cfr+A6MHPSgSWLtnjyK39Gb3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
út 17. 9. 2019 v 10:01 odesílatel Mitar <mmitar(at)gmail(dot)com> 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 it to JSON).
>
I think so is not any problem to pass binary data already. Text type "text"
and binary type "bytea" is internally very similar.
But the message doesn't any info about type, so it should be ensure so
clients understand to message and takes data in binary format.
You can overwrite pg_notify function for bytea format.
Is not possible to use NOTIFY with binary data, because this statement
doesn't allow parametrization
Pavel
>
>
> Mitar
>
> --
> http://mitar.tnode.com/
> https://twitter.com/mitar_m
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2019-09-17 08:35:22 | Re: Nondeterministic collations vs. text_pattern_ops |
Previous Message | Mitar | 2019-09-17 08:01:32 | Feature request: binary NOTIFY |