Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION
Date
Msg-id 1723211.1732656332@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION  (Paul Foerster <paul.foerster@gmail.com>)
Responses Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION
List 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
emptyresult 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



pgsql-general by date:

Previous
From: Paul Foerster
Date:
Subject: Re: PostgreSQL 15.10 update corrective action for ATTACH PARTITION/DETACH PARTITION
Next
From: shashidhar Reddy
Date:
Subject: Re: Unique key constraint Issue