Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints - Mailing list pgsql-general

From Paul Foerster
Subject Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
Date
Msg-id C978240A-915E-4AAA-B665-CB1630A11E7D@gmail.com
Whole thread Raw
In response to Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-general
Hi Alvaro,

> On 19 Nov 2024, at 17:34, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> It doesn't really matter when you do it, because the constraint only
> gets broken by running DETACH with the old server code.  You have
> already run the DETACH sometime in the past (that's how the constraint
> got broken), which means you would not run it again now to the same
> table.  The old server code will behave correctly when doing ADD / DROP
> constraint, as will the new server code.  Feel free to run it when it's
> more convenient to you.

Thanks.

> I'd advise against running ALTER TABLE DETACH until you have upgraded,
> however -- at least, for partitioned tables that have foreign keys
> pointing to other partitioned tables.

I have no influence on that. It's a third party application. In fact, I can't even do much about the applications
developedinhouse because they're too big. That means, if there is anything built into an application, then it takes
manymoons to get it out again. 

Cheers,
Paul





pgsql-general by date:

Previous
From: Paul Foerster
Date:
Subject: Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
Next
From: Adrian Klaver
Date:
Subject: Re: Help with restoring database from old version of PostgreSQL