public inbox for [email protected]  
help / color / mirror / Atom feed
From: Bruce Momjian <[email protected]>
To: Amit Langote <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: David Rowley <[email protected]>
Subject: Re: PG 18 release notes draft committed
Date: Fri, 2 May 2025 12:18:06 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+HiwqFQWzExQD6cYQsV6Lp4_PkCnGqPwELtEujc_6NTQGJDoA@mail.gmail.com>
References: <[email protected]>
	<CA+HiwqFQWzExQD6cYQsV6Lp4_PkCnGqPwELtEujc_6NTQGJDoA@mail.gmail.com>

On Fri, May  2, 2025 at 01:00:57PM +0900, Amit Langote wrote:
> 1. Speed up execution of cached plans by deferring locks on partitions
> subject to pruning (Amit Langote)
> (bb3ec16e1, d47cbf474, cbc127917, 525392d57)
> 
> 2. Speed up child EquivalenceMember lookup in planner (Yuya Watari,
> David Rowley)
> (d69d45a5a)
> 
> 3. Speed up derived clause lookup in EquivalenceClass (Ashutosh Bapat)
> (88f55bc97)
> 
> Alternatively, 2 and 3 can be combined as:
> 
> 2. Speed up partition planning by improving EquivalenceClass lookups
> (Yuya Watari, David Rowley, Ashutosh Bapat)
> 
> I think 1 should go under Partitioning, which I see is currently missing.
> 
> Any thoughts, David?
> 
> Can work on a patch if you'd like.

So, a few things.  First, these set of commits was in a group of 10 that
I added since there have been complaints in the past that optimizer
improvements were not listed and therefore patch authors were not given
sufficient credit.  That means the 209 item count for PG 18 is 10 higher
than my normal filtering would produce.

Second, looking at the items, these are a case of "X is faster", which
we don't normally mention in the release notes.  We normally mention
"faster" when it is so much faster that use cases which were not
possible before might be possible now, so it is recommended to retest.
That is what I saw this grouped item as, whereas I don't think the
individual items meet that criteria.

Also, I didn't see enough partition items to warrant a separate
partition section, and we didn't have one in PG 17 either.  We could
pull all the partition items from the sections they are already in, but
they seem more natural in the sections they are in.

I don't think most people would know what EquivalenceMember is, and even
if they did, would they be able to connect it to an SQL query?

Finally, I see the big increases in this release as being the optimizer,
monitoring, and constraints.

-- 
  Bruce Momjian  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.





view thread (147+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PG 18 release notes draft committed
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox