On 12/21/2015 02:30 PM, Chapman Flack wrote:
> On 12/21/2015 12:46 PM, Tom Lane wrote:

>> all, since we don't provide a way for extensions to hook into the DROP
>> mechanisms.  Perhaps that should be fixed.)
> That is literally *the very next* e-mail I was going to compose.
> I was looking at pg_(sh)?depend, ...
> I can probably cobble around this with some
> combination of triggers on my own table ('cause that works) and
> event triggers to grovel through the parse trees of commands that
> could affect the system object,

right, I can't event-trigger on role commands either, can I?

What's the lightest-weight object I can create that has an owner,
and whose disappearance I can be notified of?


Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to