Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul Foerster <paul(dot)foerster(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION
Date: 2024-11-26 21:25:32
Message-ID: 1723211.1732656332@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Paul Foerster <paul(dot)foerster(at)gmail(dot)com> writes:
>> On 26 Nov 2024, at 17:56, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message shashidhar Reddy 2024-11-27 02:31:39 Re: Unique key constraint Issue
Previous Message Paul Foerster 2024-11-26 19:02:33 Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION