| From: | Amit Langote <amitlangote09(at)gmail(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-19 12:06:04 |
| Message-ID: | CA+HiwqHLa06WANZYfix3OdbaESec61ye5Dwv0sgymoEBQJAu2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 19, 2019 at 8:49 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> On 2019-Mar-19, Amit Langote wrote:
>
> > Will it suffice or be OK if we skipped invoking the pre-drop callback for
> > objects that are being "indirectly" dropped? I came up with the attached
> > patch to resolve this problem, if that idea has any merit. We also get
> > slightly better error message as seen the expected/foreign_key.out changes.
>
> I don't think this works ... consider putting some partition in a
> different schema and then doing DROP SCHEMA CASCADE.
Ah, I did test DROP SCHEMA CASCADE, but only tested putting the top
table into the schema, not a partition.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-03-19 12:13:11 | Re: partitioned tables referenced by FKs |
| Previous Message | Alvaro Herrera | 2019-03-19 12:05:29 | Re: Contribution to Perldoc for TestLib module in Postgres |