| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(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:22:39 |
| Message-ID: | 20190329152239.GA29258@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2019-03-29 15:25:57 | Re: PostgreSQL pollutes the file system |
| Previous Message | Jesper Pedersen | 2019-03-29 15:19:20 | Re: partitioned tables referenced by FKs |