Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: jsonb and nested hstore
Date
Msg-id CAHyXU0wNf2Ke+yjC=HMkobYk2i-mUsE+a6f=ffksf4ZVMEi7gg@mail.gmail.com
Whole thread Raw
In response to Re: jsonb and nested hstore  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: jsonb and nested hstore  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Mon, Feb 24, 2014 at 8:46 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
> I still find the phrasing "as jsonb is more efficient for most
> purposes" to be a bit off  Basically, the text json type is faster for
> serialization/deserialization pattern (not just document preservation)
> and jsonb is preferred when storing json and doing repeated
>subdocument accesses.

Hm, I'm going to withdraw that.  I had done some testing of simple
deserialization (cast to text and the like) and noted that jsonb was
as much as 5x slower.  However, I just did some checking on
json[b]_populate_recordset though and it's pretty much a wash.

merlin



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: often PREPARE can generate high load (and sometimes minutes long unavailability)
Next
From: Andres Freund
Date:
Subject: Re: often PREPARE can generate high load (and sometimes minutes long unavailability)