From: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: partitioned tables referenced by FKs |
Date: | 2019-03-29 15:30:33 |
Message-ID: | 46a1dc32-6a62-58a5-ee5b-a0798453ad04@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 3/29/19 11:22 AM, Alvaro Herrera wrote:
> On 2019-Mar-29, Jesper Pedersen wrote:
>
>> Could expand a bit on the change to DEPENDENCY_INTERNAL instead of
>> DEPENDENCY_PARTITION_PRI / DEPENDENCY_PARTITION_SEC ?
>
> The PARTITION dependencies work in a way that doesn't do what we want.
> Admittedly, neither does INTERNAL, but at least it's less bad.
>
>> If you run "DROP TABLE t2_p32 CASCADE" the foreign key constraint is removed
>> from all of t1.
>
> Yes. CASCADE is always a dangerous tool; if you run the DROP partition
> without cascade, it explicitly lists that the constraint is going to be
> dropped.
>
> If you get in the habit of added CASCADE to all your drops, you're going
> to lose data pretty quickly. In this case, no data is lost, only a
> constraint.
>
Thanks !
Maybe the "(" / ")" in the CASCADE description should be removed from
ref/drop_table.sgml as part of this patch.
Should catalogs.sgml be updated for this case ?
Best regards,
Jesper
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-03-29 15:34:14 | Re: Online verification of checksums |
Previous Message | Stephen Frost | 2019-03-29 15:30:15 | Re: Online verification of checksums |