Re: On login trigger: take three
| От | Andres Freund |
|---|---|
| Тема | Re: On login trigger: take three |
| Дата | |
| Msg-id | 20220314000825.t7yywdubftb5cwl6@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: On login trigger: take three (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: On login trigger: take three
Re: On login trigger: take three |
| Список | pgsql-hackers |
Hi, On 2022-03-13 19:57:08 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > On 2022-03-13 23:31:03 +0100, Daniel Gustafsson wrote: > >> Something like a '-c ignore_event_trigger=<event|all>' GUC perhaps? > > > Did you mean login instead of event? > > > Something like it would work for me. It probably should be > > GUC_DISALLOW_IN_FILE? > > Why? Inserting such a setting in postgresql.conf and restarting > would be the first thing I'd think of if I needed to get out > of a problem. The only other way is to set it on the postmaster > command line, which is going to be awkward-to-impossible with > most system-provided start scripts. 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. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: