Re: Postgresql 14 partitioning advice - Mailing list pgsql-performance

From Justin Pryzby
Subject Re: Postgresql 14 partitioning advice
Date
Msg-id 20220808225515.GB19644@telsasoft.com
Whole thread Raw
In response to Re: Postgresql 14 partitioning advice  (Slava Mudry <slava44@gmail.com>)
List pgsql-performance
On Mon, Aug 08, 2022 at 03:45:11PM -0700, Slava Mudry wrote:
> Postgres 14 improved partitioning quite a bit. I used it in Postgres 9 and
> there was a lot of locking on partition hierarchy when you add/drop
> partition tables.

Note that postgres 9 didn't have native/declarative partitioning, and most
improvements in native partitioning don't apply to legacy/inheritance
partitioning.

https://www.postgresql.org/docs/devel/ddl-partitioning.html

"Native" partitioning added in v10 tends to require stronger locks for add/drop
than legacy partitioning, since partitions have associated bounds, which cannot
overlap.  The locking is improved in v12 with CREATE+ATTACH and v14 with
DETACH CONCURRENTLY+DROP.

-- 
Justin



pgsql-performance by date:

Previous
From: Slava Mudry
Date:
Subject: Re: Postgresql 14 partitioning advice
Next
From: Nico Heller
Date:
Subject: to_jsonb performance on array aggregated correlated subqueries