Re: PG 18 release notes draft committed - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: PG 18 release notes draft committed
Date
Msg-id CAH2-Wzko57+sT=FcxHHo7jnPLhh35up_5aAvogLtj_D9bATsgQ@mail.gmail.com
Whole thread Raw
In response to PG 18 release notes draft committed  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, May 22, 2025 at 10:24 PM Bruce Momjian <bruce@momjian.us> wrote:
> I see your point that we are not defining what this does.  I went with
> the attached text.

You propose the wording is "This allows muti-column btree indexes to
be used by queries that only reference the second or later indexed
columns".

I think that your wording is a big improvement. I personally would
have emphasized the absence of a "=" condition, rather than the
presence of another condition on a later column, since there are cases
where the first column is referenced but skip scan can still be used
(e.g., when there one or more inequalities on the first column, plus a
"=" condition on the second column). I can live with this wording,
though.

Thanks
--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Shaik Mohammad Mujeeb
Date:
Subject: Re: [Util] Warn and Remove Invalid GUCs
Next
From: Sami Imseih
Date:
Subject: Re: queryId constant squashing does not support prepared statements