Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Foerster <paul.foerster@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
pgsql-general list <pgsql-general@lists.postgresql.org>
Date: 2024-11-26T21:25:32Z
Lists: pgsql-general
Paul Foerster <paul.foerster@gmail.com> writes: >> On 26 Nov 2024, at 17:56, Adrian Klaver <adrian.klaver@aklaver.com> wrote: >> When you run the query again do you get the same two statements? > Yes. I can repeat the above 4 steps as much as I want. The result remains the same. I would have expected to have an empty result doing the final repeated select, but it shows exactly the same output. I would have expected an empty result too. Can you confirm that p_ci_pipelines used to be a partition of something? Can you show us the full DDL (or psql \d+ output) for the partitioned table it used to be part of, and for that matter also for p_ci_pipelines? Did the FK used to reference the whole partitioned table, or just this partition? I'm suspicious that our repair recipe might not have accounted for self-reference FKs fully, but that's just a gut feeling at this point. regards, tom lane
Commits
-
Fix broken-FK-detection query in release notes
- db54be898a68 16.10 landed
- 7f4261d9da35 14.19 landed
- 50a8959cd50b 17.6 landed
- 4620cd9c1c80 15.14 landed
- 3e75313c2bea 13.22 landed