Hi folks,
I'm trying to understand the new Index Searches field in Postgres 18
explain analyze output. I've put together a super simple test case (below)
expecting a skip scan with 2 Index Searches, one for each value in the
leading (boolean) column of the index.
In reality, instead of 2 Index Se
On Thu, Nov 6, 2025 at 2:01 PM Michael Christofides
wrote:
> I'm trying to understand the new Index Searches field in Postgres 18 explain
> analyze output. I've put together a super simple test case (below) expecting
> a skip scan with 2 Index Searches, one for each value in the leading
> (bool
On Thu, Nov 6, 2025 at 2:54 PM Peter Geoghegan wrote:
> That just leaves SK_ISNULL. We cannot assume that the index doesn't
> have any NULLs (unless the query uses IS NOT NULL directly).
Actually, that won't work here. Because the optimizer recognizes that
the leading boolean column isn't nullabl
