On Tue, Mar 19, 2019 at 8:49 PM Alvaro Herrera <alvherre@2ndquadrant.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
