Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently
Date
Msg-id 202510111834.yxmra6mxo5zp@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #18371: There are wrong constraint residues when detach hash partiton concurrently  (alvherre <alvherre@alvh.no-ip.org>)
List pgsql-bugs
On 2024-Jul-15, alvherre wrote:

> We should definitely not have this constraint on hash-partition tables
> after the detach.  However, I wonder if instead of adding it and later
> removing it as you propose, it wouldn't be better to just not add it in
> the first place.  As a first step, I tried commenting out and found that
> no interesting test fails (only alter_table.sql fails but only because
> the constraint is not there when looking for it specifically.)

Pushed a fix for this per report in
https://postgr.es/m/19070-781326347ade7c57@postgresql.org

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
<Schwern> It does it in a really, really complicated way
<crab> why does it need to be complicated?
<Schwern> Because it's MakeMaker.



pgsql-bugs by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table
Next
From: David Rowley
Date:
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade