From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Foerster <paul.foerster@gmail.com>
cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
In-reply-to: <A1FAF798-A5DB-4C44-904E-AB2675A838BF@gmail.com>
References: <A1FAF798-A5DB-4C44-904E-AB2675A838BF@gmail.com>
Comments: In-reply-to Paul Foerster <paul.foerster@gmail.com>
	message dated "Tue, 19 Nov 2024 17:11:22 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3775603.1732033502.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Nov 2024 11:25:02 -0500
Message-ID: <3775604.1732033502@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3775604.1732033502%40sss.pgh.pa.us>
Precedence: bulk

Paul Foerster <paul.foerster@gmail.com> writes:
> the PostgreSQL 15.9 release notes instruct to look out for especially de=
tached partitions with foreign key constraints. I'm in the process of upda=
ting our databases from 15.8 to 15.9 now and found a case where the select=
 statement returns a constraint.

> The release notes say nothing about when to fix that using the generated=
 add or drop statements.

Generally speaking, our release notes are addressed to someone who's
already installed the update (or a later one).

			regards, tom lane