Request a Demo
Home   >   mailing lists

Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18 - Mailing list pgsql-performance

From David Rowley
Subject Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
Date
Msg-id CAApHDvqcjH9y_ofuBB8XnFA1JPZEcYSLzGss1+i9xPTcmcHLjQ@mail.gmail.com
Whole thread Raw
In response to Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
List pgsql-performance
Tree view 
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.

David

pgsql-performance by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
Next
From: Jonathan Reis
Date:
Subject: Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18