On Sunday, July 13, 2025, Marcos Pegoraro <mar...@f10.com.br> wrote: > Em sáb., 12 de jul. de 2025 às 16:07, Tom Lane <t...@sss.pgh.pa.us> > escreveu: > >> Indeed. If we put a restriction on this case then we'd just need to >> invent a "REALLY CASCADE" option that did the more aggressive thing. >> > > I understand that it's not possible to prevent DROP ... CASCADE from > executing. However, the subsequent deletion of constraints, triggers, or > functions will affect the behavior of other schemas, so I think it's > reasonable to at least explicitly state in the log which objects were > deleted due to that command. >
Then install an event trigger and log every object that gets dropped at any time. David J.
