Re: On login trigger: take three - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: On login trigger: take three
Date
Msg-id 8F2FC11D-F0B4-41F2-BA7F-BA7F84DBF493@yesql.se
Whole thread Raw
In response to Re: On login trigger: take three  (Greg Nancarrow <gregn4422@gmail.com>)
Responses Re: On login trigger: take three
Re: On login trigger: take three
List pgsql-hackers
> On 11 Nov 2021, at 07:37, Greg Nancarrow <gregn4422@gmail.com> wrote:

> I've attached an updated patch, that essentially reinstates the v19
> patch

Thanks!  I've only skimmed it so far but it looks good, will do a more thorough
review soon.

+        This flag is used to avoid extra lookups on the pg_event_trigger table during each backend startup.
This should be <structname>pg_event_trigger</structname>.  Sorry, missed that
one at that last read-through.

> - dathaslogintriggers -> dathasloginevttriggers flag rename (too
> long?)

I'm not crazy about this name, "evt" is commonly the abbreviation of "event
trigger" (used in evtcache.c etc) so "dathasloginevt" would IMO be better.
That being said, that's still not a very readable name, maybe someone else has
an even better suggestion?

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: parallel vacuum comments
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Partial foreign key updates in referential integrity triggers