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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Jonathan Reis <jon(dot)reis(at)conevity(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Olof Salberger <olof(dot)salberger(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
Date: 2025-10-23 22:54:04
Message-ID: CAApHDvqcjH9y_ofuBB8XnFA1JPZEcYSLzGss1+i9xPTcmcHLjQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, 24 Oct 2025 at 09:38, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jonathan Reis 2025-10-24 02:14:15 Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18
Previous Message Laurenz Albe 2025-10-23 20:38:11 Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18