Re: InvokeObjectPostAlterHook() vs. CommandCounterIncrement() - Mailing list pgsql-hackers

From Noah Misch
Subject Re: InvokeObjectPostAlterHook() vs. CommandCounterIncrement()
Date
Msg-id 20130721160729.GB126816@tornado.leadboat.com
Whole thread Raw
In response to Re: InvokeObjectPostAlterHook() vs. CommandCounterIncrement()  (Ants Aasma <ants.aasma@eesti.ee>)
List pgsql-hackers
On Sun, Jul 21, 2013 at 11:44:51AM +0300, Ants Aasma wrote:
> On Jul 21, 2013 4:06 AM, "Noah Misch" <noah@leadboat.com> wrote:
> > If these hooks will need to apply to a larger operation, I
> > think that mandates a different means to reliably expose the before/after
> > object states.
> 
> I haven't checked the code to see how it would fit the API, but what about
> taking a snapshot before altering and passing this to the hook. Would there
> be other issues besides performance? If the snapshot is taken only when
> there is a hook present then the performance can be fixed later.

That would work.

-- 
Noah Misch
EnterpriseDB                                 http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Preventing tuple-table leakage in plpgsql
Next
From: Tom Lane
Date:
Subject: Re: Preventing tuple-table leakage in plpgsql