| From: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints |
| Date: | 2024-11-19 16:11:22 |
| Message-ID: | A1FAF798-A5DB-4C44-904E-AB2675A838BF@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
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?
https://www.postgresql.org/docs/15/release-15-9.html
Section E.1.2, changelog entry 5.
Any insight would be highly appreciated. Thanks in advance.
Cheers
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-11-19 16:17:16 | Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key constraints |
| Previous Message | David G. Johnston | 2024-11-19 15:55:39 | Re: Specifying columns returned by a function, when the function is in a SELECT column list? |