From: Chapman Flack <chap@anastigmatix.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: tracking owner of extension-managed objects
Date: Mon, 21 Dec 2015 15:09:48 -0500
Message-ID: <56785C8C.6060006@anastigmatix.net> (raw)
In-Reply-To: <56785344.6080803@anastigmatix.net>
References: <56783412.6090005@anastigmatix.net>
<3486.1450720004@sss.pgh.pa.us>
<56785344.6080803@anastigmatix.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: chap@anastigmatix.net, tgl@sss.pgh.pa.us
Subject: Re: tracking owner of extension-managed objects
In-Reply-To: <56785C8C.6060006@anastigmatix.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox