Re: additional json functionality - Mailing list pgsql-hackers

From Greg Stark
Subject Re: additional json functionality
Date
Msg-id CAM-w4HMnBpK=g2R=zydeXHPKk+dQfwHskVCcqc082tVAViu-PA@mail.gmail.com
Whole thread
In response to Re: additional json functionality  (Josh Berkus <josh@agliodbs.com>)
Responses Re: additional json functionality
Re: additional json functionality
Re: additional json functionality
List pgsql-hackers

On Sat, Nov 16, 2013 at 12:32 AM, Josh Berkus <josh@agliodbs.com> wrote:
On 11/15/2013 04:00 PM, David Johnston wrote:
> Looking at this a different way: could we just implement BSON and leave json
> alone?
>
> http://bsonspec.org/

In short?  No.

For one thing, our storage format is different from theirs (better,
frankly), and as a result is not compliant with their "standard".

Not being super familiar with either BSON our JSONB what advantages are we gaining from the difference?

It might be interesting if we supported the same binary representation so we could have a binary send/recv routines that don't need to do any serialization/deserialization. Especially since a standard format would potentially be skipping the serialization/deserialization on both the server and client.



--
greg

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: -d option for pg_isready is broken
Next
From: Tom Lane
Date:
Subject: WITH ORDINALITY versus column definition lists