Re: First draft of PG 17 release notes - Mailing list pgsql-hackers

From David Rowley
Subject Re: First draft of PG 17 release notes
Date
Msg-id CAApHDvqmW0wQRam4paRbHvLQA+w5CJOCno4BCu=NFRLRhYhtRw@mail.gmail.com
Whole thread Raw
In response to Re: First draft of PG 17 release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: First draft of PG 17 release notes
List pgsql-hackers
On Sun, 26 May 2024 at 15:57, Bruce Momjian <bruce@momjian.us> wrote:
> Agreed.  I changed it to:
>
>         Allow btree indexes to more efficiently find a set of values, such as
>         those supplied by IN subqueries
>
> Is that good?

I think this needs further adjustment.  An "IN subquery" is an IN
clause which contains a subquery.  As far as I understand it,
5bf748b86 does nothing to improve those. It's there to improve IN with
a set of values such as IN(1,2,3).

Maybe "IN subqueries" can be replaced with "an SQL IN clause".

David



pgsql-hackers by date:

Previous
From: arne.roland@malkut.net
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join
Next
From: Bruce Momjian
Date:
Subject: Re: First draft of PG 17 release notes