Re: Jsonb extraction very slow - Mailing list pgsql-general

From Tom Lane
Subject Re: Jsonb extraction very slow
Date
Msg-id 28861.1470923152@sss.pgh.pa.us
Whole thread Raw
In response to Re: Jsonb extraction very slow  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Jsonb extraction very slow  ("hari.prasath" <hari.prasath@zohocorp.com>)
Re: Jsonb extraction very slow  (Merlin Moncure <mmoncure@gmail.com>)
Re: Jsonb extraction very slow  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-general
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
> I never dug into why. As Tom posited, decompression might explain the
> time to get a single key out. Getting 10 keys instead of just 1 wasn't
> 10x more expensive, but it was significantly more expensive than just
> getting a single key.

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.

            regards, tom lane


pgsql-general by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Jsonb extraction very slow
Next
From: Andy Colson
Date:
Subject: Re: pglogical cross subscribe