| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| 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-24 05:04:16 |
| Message-ID: | b0991c2d8348da5b97bb0cdb1fe7a3d6a21a0df6.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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(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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-10-24 12:38:57 | Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18 |
| Previous Message | Jonathan Reis | 2025-10-24 02:14:15 | Re: Performance implications of partitioning by UUIDv7 range in PostgreSQL v18 |