Horton

Re: WIP Patch: Add a function that returns binary JSONB as a bytea

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

View thread View on postgr.es
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Merlin Moncure <mmoncure@gmail.com>, Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Stephen Frost <sfrost@snowman.net>, kevinvan@shift.com, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-11-02T21:02:24Z
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

Commits

  1. Build de-escaped JSON strings in larger chunks during lexing