Re: GIN JSONB path index is not always used

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Tomasz Szymański <lime129(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: GIN JSONB path index is not always used
Date: 2023-10-17 14:17:26
Message-ID: 93a4f67a1a2fea0a6f59a1f6f314b173f4a27d58.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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, no JSON.

Yours,
Laurenz Albe

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Janes 2023-10-17 17:05:42 Re: GIN JSONB path index is not always used
Previous Message Tomasz Szymański 2023-10-17 13:48:41 GIN JSONB path index is not always used