Horton

Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18

Laurenz Albe <laurenz.albe@cybertec.at>

View thread
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Jonathan Reis <jon.reis@conevity.com>, Greg Sabino Mullane <htamfids@gmail.com>, Olof Salberger <olof.salberger@gmail.com>, pgsql-performance@lists.postgresql.org
Date: 2025-10-24T05:04:16Z
Lists: pgsql-performance 
On Fri, 2025-10-24 at 11:54 +1300, David Rowley wrote:
> On Fri, 24 Oct 2025 at 09:38, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> > I recommend that you create a primary key on each partition rather than having one
> > on the partitioned table.
> 
> It might be worth mentioning that doing that would forego having the
> ability to reference the partitioned table in a foreign key
> constraint.

Right, but referencing a partitioned table with a foreign key is a mixed blessing
anyway: you could no longer drop partitions from the partitioned table without
scanning the referencing table to verify that the foreign key is not violated.

Yours,
Laurenz Albe