Hi hackers, The attached v40 patch is a fresh rebase on master branch to actualize the state before the upcoming commitfest. Nothing has changed beyond rebasing.
And just for convenience, here is a link to the exact message of the thread describing the current approach: https://www.postgresql.org/message-id/CAMEv5_vg4aJOoUC74XJm%2B5B7%2BTF1nT-Yhtg%2BawtBOESXG5Grfg%40mail.gmail.com -- best regards, Mikhail A. Gribkov e-mail: youzh...@gmail.com *http://www.flickr.com/photos/youzhick/albums <http://www.flickr.com/photos/youzhick/albums>* http://www.strava.com/athletes/5085772 phone: +7(916)604-71-12 Telegram: @youzhick On Wed, Mar 22, 2023 at 10:38 PM Daniel Gustafsson <dan...@yesql.se> wrote: > > On 22 Mar 2023, at 18:54, Robert Haas <robertmh...@gmail.com> wrote: > > > Basically, I think 0001 is a good idea -- I'm much more nervous about > > 0002. I think we should get 0001 polished up and committed. > > Correct me if I'm wrong, but I believe you commented on v27-0001 of the > login > event trigger patch series? Sorry about the confusion if so, this is a > very > old and lengthy thread with many twists and turns. This series was closed > downthread when the original authors of login EVT left, and the 0001 GUC > patch > extracted into its own thread. That patch now lives at: > > https://commitfest.postgresql.org/42/4013/ > > This thread was then later revived by Mikhail Gribkov but without 0001 > instead > referring to the above patch for that part. > > The new patch for 0001 is quite different, and I welcome your eyes on that > since I agree with you that it would be a good idea. > > -- > Daniel Gustafsson > > > >
v40-On_client_login_event_trigger.patch
Description: Binary data
