From: | Zhihong Yu <zyu(at)yugabyte(dot)com> |
---|---|
To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: handling multiple matching constraints in DetachPartitionFinalize() |
Date: | 2022-08-23 17:27:53 |
Message-ID: | CALNJ-vQx1JqRKAvFK+9va-6kh8fe+-=S=+Typo5fGs+CUOhJtA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 23, 2022 at 10:10 AM Zhihong Yu <zyu(at)yugabyte(dot)com> wrote:
> Hi,
> I was looking at the following code in DetachPartitionFinalize():
>
> /* If there's a constraint associated with the index, detach it
> too */
> constrOid =
> get_relation_idx_constraint_oid(RelationGetRelid(partRel),
> idxid);
>
> As mentioned in email thread `parenting a PK constraint to a self-FK one`,
> there may be multiple matching constraints, I think we should
> call ConstraintSetParentConstraint() for each of them.
>
> This means adding a helper method similar to
> get_relation_idx_constraint_oid() which finds constraint and calls
> ConstraintSetParentConstraint().
>
> I am preparing a patch.
> Please let me know if my proposal makes sense.
>
> Thanks
>
This is what I came up with.
Attachment | Content-Type | Size |
---|---|---|
detach-constraints.patch | application/octet-stream | 3.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-08-23 17:28:50 | Re: SQL/JSON features for v15 |
Previous Message | Andres Freund | 2022-08-23 17:27:18 | Re: SQL/JSON features for v15 |