Re: Add jsonb_compact(...) for whitespace-free jsonb to text - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Add jsonb_compact(...) for whitespace-free jsonb to text
Date
Msg-id CAKFQuwa6A8OnWwz_5anL6ZsvXcUXzs+aEnnRMCWdLZ+9d3XJww@mail.gmail.com
Whole thread Raw
In response to Re: Add jsonb_compact(...) for whitespace-free jsonb to text  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Fri, Apr 29, 2016 at 7:15 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
Andrew mentions several solutions.  I like them all except I would
prefer not to introduce a GUC for controlling the output format.  I do
not think it's a good idea to set the expectation that clients can
rely on text out byte for byte for any type including json.

​+1​

​I agree on the GUC point and on the general ​desirability of making jsonb output not include insignificant whitespace.

​There seems to be enough coders who agree to this principle: could one of you please write a patch and start a new thread specifically for this change.  If we go that route the need for the subject of this thread becomes moot.

Thanks!

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg9.6 segfault using simple query (related to use fk for join estimates)
Next
From: Merlin Moncure
Date:
Subject: Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0