Re: On login trigger: take three
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
Greg Nancarrow <gregn4422@gmail.com>,
Ivan Panchenko <wao@mail.ru>,
Teodor Sigaev <teodor@sigaev.ru>,
Ibrar Ahmed <ibrar.ahmad@gmail.com>,
vignesh C <vignesh21@gmail.com>,
Pavel Stehule <pavel.stehule@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Amit Kapila <amit.kapila16@gmail.com>,
Masahiko Sawada <sawada.mshk@gmail.com>
Date: 2022-03-14T13:47:09Z
Lists: pgsql-hackers
Attachments
- v26-0003-Add-IGNORE_EVENT_TRIGGER_LOGIN.patch (application/octet-stream) patch v26-0003
- v26-0002-v25-of-event-trigger-patch.patch (application/octet-stream) patch v26-0002
- v26-0001-Provide-a-GUC-for-temporarily-ignoring-event-tri.patch (application/octet-stream) patch v26-0001
> On 14 Mar 2022, at 01:08, Andres Freund <andres@anarazel.de> wrote: > I was thinking that the way to use it would be to specify it as a client > option. Like PGOPTIONS='-c ignore_event_trigger=login' psql. Attached is a quick PoC/sketch of such a patch, where 0001 adds a guc, 0002 is the previously posted v25 login event trigger patch, and 0003 adapts is to allow ignoring it (0002/0003 split only for illustrative purposes of course). Is this along the lines of what you were thinking? -- Daniel Gustafsson https://vmware.com/
Commits
-
Fix some typos in event trigger docs
- 5fce30e77fe1 17.0 landed
-
Use heap_inplace_update() to unset pg_database.dathasloginevt
- 8be93177c46b 17.0 landed
-
Remove the flaky check in event_trigger_login regression test
- 4b885d01f967 17.0 landed
-
Fix instable 006_login_trigger.pl test
- 06be01eb266b 17.0 landed
-
Add support event triggers on authenticated login
- e83d1b0c40cc 17.0 landed
-
Add GUC for temporarily disabling event triggers
- 7750fefdb2b8 17.0 landed
-
Fix typo in reference to __FreeBSD__.
- e52f8b301ed5 16.0 cited
-
Restore robustness of TAP tests that wait for postmaster restart.
- f452aaf7d4a9 14.0 cited
-
Restore the portal-level snapshot after procedure COMMIT/ROLLBACK.
- 84f5c2908dad 14.0 cited