public inbox for [email protected]
help / color / mirror / Atom feedRe: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
2+ messages / 2 participants
[nested] [flat]
* Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
@ 2024-11-19 16:34 Alvaro Herrera <[email protected]>
2024-11-19 19:16 ` Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints Paul Foerster <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Alvaro Herrera @ 2024-11-19 16:34 UTC (permalink / raw)
To: Paul Foerster <[email protected]>; +Cc: pgsql-general list <[email protected]>
Hi Paul,
On 2024-Nov-19, Paul Foerster wrote:
> the PostgreSQL 15.9 release notes instruct to look out for especially
> detached partitions with foreign key constraints. I'm in the process
> of updating 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.
>
> Do I want/need to do that before or after I exchange the software? And
> if it is to be done on a particular of the two releases, why is that?
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.
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.
Thanks,
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Postgres is bloatware by design: it was built to house
PhD theses." (Joey Hellerstein, SIGMOD annual conference 2002)
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints
2024-11-19 16:34 Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints Alvaro Herrera <[email protected]>
@ 2024-11-19 19:16 ` Paul Foerster <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Paul Foerster @ 2024-11-19 19:16 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: pgsql-general list <[email protected]>
Hi Alvaro,
> On 19 Nov 2024, at 17:34, Alvaro Herrera <[email protected]> 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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-11-19 19:16 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-11-19 16:34 Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints Alvaro Herrera <[email protected]>
2024-11-19 19:16 ` Paul Foerster <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox