>>"Bitmap Heap Scan on articles (cost=16.25..135.64 rows=33 width=427)
>> (actual time=6.425..43.603 rows=18584 loops=1)"
>> " Recheck Cond: (data @> ‘{"locked": true}'::jsonb)"
>> " Heap Blocks: exact=1496"
>> " Buffers: shared hit=1504"
>> " -> Bitmap Index Scan on idx_data (cost=0.00..16
Christian Weyer writes:
> On 01.02.15 22:06, "Josh Berkus" wrote:
>> Please send us the output of EXPLAIN ( ANALYZE ON, BUFFERS ON ) so that
>> we can see what the query is actually doing, rather than just what the
>> plan was.
> Sure. Here we go:
> "Bitmap Heap Scan on articles (cost=16.25..1
On 01.02.15 22:06, "Josh Berkus" wrote:
>Please send us the output of EXPLAIN ( ANALYZE ON, BUFFERS ON ) so that
>we can see what the query is actually doing, rather than just what the
>plan was.
>
>--
>Josh Berkus
>PostgreSQL Experts Inc.
>http://pgexperts.com
Sure. Here we go:
"Bitmap Hea
On 01/31/2015 11:02 AM, Christian Weyer wrote:
> Just checked: the execution time is the same when I drop the index.
>
> Execution plan with index:
> ---
> "Bitmap Heap Scan on articles (cost=16.25..135.64 rows=33 width=427)"
> " Recheck Cond: (data @> '{"locked": true}'::jsonb)"
> " -> Bitmap
;locked": true}'::jsonb)"
---
-C.
From: Christian Weyer
Date: Samstag, 31. Januar 2015 17:00
To: "pgsql-performance@postgresql.org<mailto:pgsql-performance@postgresql.org>"
Subject: [PERFORM] Unexpected (bad) performance when querying indexed JSONB
column
Hi all,
The pg
Hi all,
The pg version in question is the latest 9.4., running on Windows.
For testing out the NoSQL features of pg I have a simple table called
‘articles’ with a column called ‘data’.
There is an index on ‘data’ like this:
CREATE INDEX idx_data ON articles USING gin (data jsonb_path_ops);
T
