| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Slava Mudry <slava44(at)gmail(dot)com> |
| Cc: | Rick Otten <rottenwindfish(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgresql 14 partitioning advice |
| Date: | 2022-08-08 22:55:15 |
| Message-ID: | 20220808225515.GB19644@telsasoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Heller | 2022-08-12 18:49:58 | to_jsonb performance on array aggregated correlated subqueries |
| Previous Message | Slava Mudry | 2022-08-08 22:45:11 | Re: Postgresql 14 partitioning advice |