| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, kevinvan(at)shift(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP Patch: Add a function that returns binary JSONB as a bytea |
| Date: | 2018-11-02 21:02:24 |
| Message-ID: | bfaf8154-db42-1c2c-c72a-518d927e9c99@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/02/2018 11:34 AM, Merlin Moncure wrote:
>
> Binary format consuming applications already have to deal with these
> kinds of issues. We already expose internal structures in the other
> functions -- not sure why jsonb is held to a different standard. For
> other data types where format changes were made, the standard of
> 'caveat version' was in place to protect the user. For jsonb we
> decided to implement a version flag within the type itself, which I
> thought mistake at the time -- better to have a version header in the
> COPY BINARY if needed.
>
jsonb_send does output a version header, as I pointed out upthread.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-11-02 21:15:41 | Re: WIP Patch: Add a function that returns binary JSONB as a bytea |
| Previous Message | Bruno Wolff III | 2018-11-02 21:01:34 | Re: Should pg 11 use a lot more memory building an spgist index? |