Re: tracking owner of extension-managed objects - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: tracking owner of extension-managed objects
Date
Msg-id 56785C8C.6060006@anastigmatix.net
Whole thread Raw
In response to Re: tracking owner of extension-managed objects  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: tracking owner of extension-managed objects
List pgsql-hackers
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?

-Chap



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates
Next
From: Tom Lane
Date:
Subject: Coding note: truncating with strlcpy() is not such a hot idea