Re: GIN JSONB path index is not always used

2023-10-23 Thread Jeff Janes
On Mon, Oct 23, 2023 at 6:33 AM Tomasz Szymański wrote: > Limit (cost=0.00..1184.30 rows=21 width=4) (actual > time=1567.136..1619.956 rows=1 loops=1) >-> Seq Scan on account_user (cost=0.00..256768.27 rows=4553 width=4) > (actual time=1567.135..1619.953 rows=1 loops=1) > It thinks the

Re: GIN JSONB path index is not always used

2023-10-23 Thread Tomasz Szymański
Sorry for missing analyze and buffers, we did only had these plans at the time, providing ones performed with such: When it does us an index: --+ Limit (cost=255.29..32

Re: GIN JSONB path index is not always used

2023-10-17 Thread Jeff Janes
On Tue, Oct 17, 2023 at 10:09 AM Tomasz Szymański wrote: > - Database version: 11.18 That is pretty old. It is 3 bug-fix releases out of date even for its major version, and the major version itself is just about to reach EOL and is missing relevant improvements. - Plan when it uses an index >

Re: GIN JSONB path index is not always used

2023-10-17 Thread Laurenz Albe
On Tue, 2023-10-17 at 15:48 +0200, Tomasz Szymański wrote: > Hello! We have an issue with database planner choosing really expensive > sequence scan instead of an index scan in some cases. To analyze that, we'd need the output from EXPLAIN (ANALYZE, BUFFERS) SELECT ... Plain text format please, n