Re: Adding missing object access hook invocations
Mark Dilger <mark.dilger@enterprisedb.com>
From: Mark Dilger <mark.dilger@enterprisedb.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@lists.postgresql.org>,
Kohei KaiGai <kaigai@heterodb.com>,
Adam Brightwell <adam.brightwell@crunchydata.com>
Date: 2020-03-17T00:58:51Z
Lists: pgsql-hackers
> On Mar 16, 2020, at 5:14 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > On 2020-Mar-16, Mark Dilger wrote: > >> Hackers, >> >> While working on object access hooks, I noticed several locations where I would expect the hook to be invoked, but no actual invocation. I think this just barely qualifies as a bug. It's debatable because whether it is a bug depends on the user's expectations and whether not invoking the hook in these cases is defensible. Does anybody have any recollection of an intentional choice not to invoke in these locations? > > Hmm, possibly the create-time calls are missing. It looks to me that both the create and alter calls are missing. > > I'm surprised about the InvokeObjectDropHook calls though. Doesn't > deleteOneObject already call that? If we have more calls elsewhere, > maybe they are redundant. I think we should only have those for > "shared" objects. Yeah, you are right about the drop hook being invoked elsewhere for dropping ACCESS METHOD and STATISTICS. Sorry for the noise. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add missing invocations to object access hooks
- a995b371ae29 13.0 landed