From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: dropping partitioned tables without CASCADE |
Date: | 2017-02-21 06:51:53 |
Message-ID: | 97113cd7-07b1-9d25-d029-66f9a86c66d9@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2017/02/21 15:35, Amit Langote wrote:
>> drop table list_parted cascade;
>> -NOTICE: drop cascades to 3 other objects
>> -DETAIL: drop cascades to table part_ab_cd
>> probably we should remove cascade from there, unless you are testing CASCADE
>> functionality. Similarly for other blocks like
>> drop table range_parted cascade;
Oops, failed to address this in the last email. Updated patches attached.
Thanks,
Amit
Attachment | Content-Type | Size |
---|---|---|
0001-Allow-dropping-partitioned-table-without-CASCADE.patch | text/x-diff | 12.9 KB |
0002-Add-regression-tests-foreign-partition-DDL.patch | text/x-diff | 14.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-02-21 07:51:34 | Re: PATCH: Batch/pipelining support for libpq |
Previous Message | Michael Paquier | 2017-02-21 06:50:33 | Re: Provide list of subscriptions and publications in psql's completion |