| From: | "hari(dot)prasath" <hari(dot)prasath(at)zohocorp(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jim Nasby" <Jim(dot)Nasby(at)BlueTreble(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Jsonb extraction very slow |
| Date: | 2016-08-12 04:31:38 |
| Message-ID: | 1567d050e6e.c23a53313551.8323271350561778673@zohocorp.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>What were you doing to "get ten keys out"? If those were ten separate
>JSON operators, they'd likely have done ten separate decompressions.
>You'd have saved something by having the TOAST data already fetched into
>shared buffers, but it'd still hardly be free.
Now i got the point. Initially, i thought for n keys to extract from json only one time the full json is decompressed. But it's actually decompressing n times for n keys.
Thanks
- Harry
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Sewell | 2016-08-12 05:39:58 | Critical failure of standby |
| Previous Message | Chris Travers | 2016-08-12 03:27:42 | Re: Postgres Pain Points 2 ruby / node language drivers |