| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-24 15:08:43 |
| Message-ID: | CAHyXU0wNf2Ke+yjC=HMkobYk2i-mUsE+a6f=ffksf4ZVMEi7gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 24, 2014 at 8:46 AM, Merlin Moncure <mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-24 15:09:13 | Re: often PREPARE can generate high load (and sometimes minutes long unavailability) |
| Previous Message | Pavel Stehule | 2014-02-24 15:02:28 | Re: often PREPARE can generate high load (and sometimes minutes long unavailability) |