From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: json (b) and null fields |
Date: | 2014-09-29 20:26:56 |
Message-ID: | 5429C090.8040500@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/29/2014 04:14 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 09/29/2014 03:23 PM, Pavel Stehule wrote:
>>> It is better than nothing, but it is not nice for JSON due 2x parsing.
>> JSON parsing is actually pretty darn fast. Every json (as opposed to
>> jsonb) function reparses the json. It's true that this is not nearly as
>> fast as processing jsonb, but I think for this purpose it's probably not
>> too bad.
> More to the point, the way to fix any concerns about double parsing is to
> create row_to_jsonb(), not to plaster a bunch of options on row_to_json().
row_to_jsonb would be completely redundant with to_jsonb() in my recent
patch.
And I don't want to add options like this there for the same reasons I
didn't want them in row_to_json().
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-09-29 20:28:55 | Re: open items for 9.4 |
Previous Message | Robert Haas | 2014-09-29 20:21:20 | Re: test_shm_mq failing on anole (was: Sending out a request for more buildfarm animals?) |