Re:Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on a hash partition table

ocean_li_996 <ocean_li_996@163.com>

From: ocean_li_996 <ocean_li_996@163.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: "mohen.lhy@alibaba-inc.com" <mohen.lhy@alibaba-inc.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, robertmhaas@gmail.com
Date: 2025-10-10T17:14:49Z
Lists: pgsql-bugs

Attachments

Hi, Álvaro
At 2025-10-10 19:03:08, "Álvaro Herrera" <alvherre@kurilemu.de> wrote:
>On 2025-Oct-10, ocean_li_996 wrote:
>
>> Since there has been no update in this thread for a few days, I
>> reached out to the primary committer for this functionality.
>

>Yes, this is buggy, and has been reported previously (#18371).


Thanks for your feedback. It seems I might have overlooked something.
At first, I assumed this was expected behavior, and after searching
the pgsql-hackers archives I did not find any related threads. I also
realize I haven’t checked pgsql-bugs.
>I'll fix
>it before the November minors, probably by removing the step of creating
>the constraints during detach.  I think for stable branches I'll do that
>only for hash partitioning, to avoid breaking workloads that might
>depend on those constraints, but for branch master I'll do it for all
>partitioning strategies.

Based on the discussion in #18371 and my own investigation, I think the
proposed fix is appropriate. I’m attaching patches for both the stable
and master branches, FYI.


--
regards
Haiyang Li