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

From: songjinzhou <tsinghualucky912(at)foxmail(dot)com>
To: ocean_li_996 <ocean_li_996(at)163(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: mohen(dot)lhy(at)alibaba-inc(dot)com <mohen(dot)lhy(at)alibaba-inc(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>, robertmhaas <robertmhaas(at)gmail(dot)com>
Subject: Re:Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on ahash partition table
Date: 2025-10-11 02:00:54
Message-ID: tencent_EA7D63A94134796E9642452AF86235FA3B08@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello hackers, Haiyang. I think the direct deletion of the DetachAddConstraintIfNeeded function in the patch above might not be a good idea. Will this create new problems?

Of the two solutions Haiyang mentioned earlier, is the second one more appropriate? Should it be deleted after detaching? For example, somewhere in the DetachPartitionFinalize function?

Of course, these are just my personal thoughts. Thank you.

songjinzhou
tsinghualucky912(at)foxmail(dot)com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message ocean_li_996 2025-10-11 08:02:59 Re: BUG #19070: issue with DETACH PARTITION CONCURRENTLY on ahash partition table
Previous Message Marco Boeringa 2025-10-10 21:36:37 Re: Potential "AIO / io workers" inter-worker locking issue in PG18?