Re: PG 18 release notes draft committed

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 18 release notes draft committed
Date: 2025-05-23 14:01:13
Message-ID: CAH2-Wzko57+sT=FcxHHo7jnPLhh35up_5aAvogLtj_D9bATsgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 22, 2025 at 10:24 PM Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-05-23 14:05:54 Re: queryId constant squashing does not support prepared statements
Previous Message Shaik Mohammad Mujeeb 2025-05-23 14:01:06 Re: [Util] Warn and Remove Invalid GUCs