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

From Bruce Momjian
Subject Re: PG 18 release notes draft committed
Date
Msg-id aBpr_L59RUEiBHso@momjian.us
Whole thread Raw
In response to Re: PG 18 release notes draft committed  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Tue, May  6, 2025 at 03:08:13PM +0900, Amit Langote wrote:
> > 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?
> 
> Thanks for splitting these (cf847d634). I think the text for the
> locking item should mention “during execution,” as David also
> suggested. Again, I don’t think this change belongs under Optimizer
> since it doesn’t really affect the planner -- it’s mainly an executor
> improvement. Maybe the General Performance section is a better fit.

Yes, good idea, done.

> Also, just to clarify why the individual items are meaningful
> performance improvements:
> 
> * Locking change: Executing cached plans involving hundreds or
> thousands of partitions was bottlenecked by locking; with this change,
> execution is now roughly 20x faster with 1000 partitions.
> 
> * Planning time improvements: Planning certain commonly used queries
> against partitioned tables when they don’t use partition pruning is
> now roughly 20x faster with 1000 partitions.

That's impressive!

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

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



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: queryId constant squashing does not support prepared statements
Next
From: Sami Imseih
Date:
Subject: Re: POC: Parallel processing of indexes in autovacuum