From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add jsonb_compact(...) for whitespace-free jsonb to text |
Date: | 2016-04-25 01:16:22 |
Message-ID: | 571D6FE6.5080604@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/24/2016 06:02 PM, Sehrope Sarkuni wrote:
>
> AFAIK, there's also no guarantee on the specific order of the
> resulting properties in the text representation either. I would
> suppose it's fixed for a given jsonb value within a database major
> version but across major versions it could change (if the underlying
> representation changes).
The order is fixed and very unlikely to change, as it was chosen quite
deliberately to help ensure efficient processing. Any change in on-disk
representation of data types is something we work very hard to avoid, as
it makes it impossible to run pg_upgrade.
It's true that the storage order of keys is not terribly intuitive.
Note that the json type, unlike jsonb, preserves exactly the white space
and key order of its input. In fact, the input is exactly what it stores.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2016-04-25 01:27:33 | Re: Add jsonb_compact(...) for whitespace-free jsonb to text |
Previous Message | Bruce Momjian | 2016-04-25 00:25:59 | Re: Rename max_parallel_degree? |