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

songjinzhou <tsinghualucky912@foxmail.com>

From: songjinzhou <tsinghualucky912@foxmail.com>

To: ocean_li_996 <ocean_li_996@163.com>, Á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 <robertmhaas@gmail.com>

Date: 2025-10-11T02:00:54Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Stop creating constraints during DETACH CONCURRENTLY
- ea06f97eeb33 17.7 landed
- bdae98495660 15.15 landed
- b835759ec7e8 16.11 landed
- b753be38a4a2 14.20 landed
- 3231fd045522 19 (unreleased) landed
- 08c037dff961 18.1 landed

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@foxmail.com