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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
