From: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints |
Date: | 2024-11-19 19:16:28 |
Message-ID: | C978240A-915E-4AAA-B665-CB1630A11E7D@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Alvaro,
> On 19 Nov 2024, at 17:34, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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 developed inhouse because they're too big. That means, if there is anything built into an application, then it takes many moons to get it out again.
Cheers,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-11-19 19:45:16 | Re: Using Expanded Objects other than Arrays from plpgsql |
Previous Message | Paul Foerster | 2024-11-19 19:12:59 | Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints |