Re: InvokeObjectPostAlterHook() vs. CommandCounterIncrement()

From: Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: kaigai(at)kaigai(dot)gr(dot)jp, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: InvokeObjectPostAlterHook() vs. CommandCounterIncrement()
Date: 2013-07-21 08:44:51
Message-ID: CA+CSw_v3Dw18raCrFtOq3uHV3U5MaCxmCzH_K1QuJnakeB=SRQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 21, 2013 4:06 AM, "Noah Misch" <noah(at)leadboat(dot)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.

Regards,
Ants Aasma

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Миша Тюрин 2013-07-21 14:01:09 Wal sync odirect
Previous Message Mag Gam 2013-07-21 06:23:05 Mag Gam