On 01/29/2014 12:46 PM, Merlin Moncure wrote:
> I think the opening paragraphs contrasting json/jsonb be needs
> refinement. json is going to be slightly faster than jsonb for input
> *and* output. For example, in one application I store fairly large
> json objects containing pre-compiled static polygon data that is
> simply flipped up to google maps. This case will likely be pessimal
> for jsonb. For the next paragaph, I'd like to expand it a bit on
> 'specialized needs' and boil it down to specific uses cases.
> Basically, json will likely be more compact in most cases and slightly
> faster for input/output; jsonb would be preferred in any context
> where processing, or searching or extensive server side parsing is
> employed.
>
> If you agree, I'd be happy to do that...
Please take a stab at it, I'll be happy to revise it.
I was working on doing a two-column table comparison chart; I still
think that's the best way to go.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
