Re: Bug in detaching a partition with a foreign key.

From: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Amul Sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in detaching a partition with a foreign key.
Date: 2025-01-21 09:44:51
Message-ID: 202501210944.xxwv26wzh74k@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Jan-20, Sami Imseih wrote:

> Patch looks good to me, but I am not sure about this part of the comment:
>
> "Only the topmost one is to be considered here; the child constraints
> must be left alone,"
>
> In this case, none of the pg_constraint entries are actually considered. right?

Right. The parent one because it has conparentid = 0, the others
because their parent constraint is in the list.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2025-01-21 10:03:58 Re: table_tuple_lock's snapshot argument
Previous Message jian he 2025-01-21 09:29:30 Re: Non-text mode for pg_dumpall