MIME-Version: 1.0
References: 
 <CAE_7N37MopcS6SYmsphE7UxQ9bJTyvgsmVb-NyCncy7fzkiC4Q@mail.gmail.com>
 <CAE_7N37Amq_G6bZDpv9tbxcZJNGVhSv8mt2MJgdZTqGO5Pdbnw@mail.gmail.com>
 <CAD39LRHMO7nEKhub=RyeZH=+Qw=qo6gSNuByDLWsR9-EDmGjhg@mail.gmail.com>
 <CAKAnmmJq3_wFNp4RN15t_YRv9xARVby7=-4PrADwPuaQQYC6JA@mail.gmail.com>
 <CAE_7N35fiC7Rq03hWutO3tPGfADQeO_gQzKHru1iNiASmUdsPQ@mail.gmail.com>
 <cc128c674065c06ebc0d1eb5e76fa2598e78c1c9.camel@cybertec.at>
In-Reply-To: <cc128c674065c06ebc0d1eb5e76fa2598e78c1c9.camel@cybertec.at>
From: David Rowley <dgrowleyml@gmail.com>
Date: Fri, 24 Oct 2025 11:54:04 +1300
Message-ID: 
 <CAApHDvqcjH9y_ofuBB8XnFA1JPZEcYSLzGss1+i9xPTcmcHLjQ@mail.gmail.com>
Subject: Re: Performance implications of partitioning by UUIDv7 range in
 PostgreSQL v18
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Jonathan Reis <jon.reis@conevity.com>,
 Greg Sabino Mullane <htamfids@gmail.com>,
	Olof Salberger <olof.salberger@gmail.com>,
 pgsql-performance@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAApHDvqcjH9y_ofuBB8XnFA1JPZEcYSLzGss1%2Bi9xPTcmcHLjQ%40mail.gmail.com>
Precedence: bulk

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