Re: On login trigger: take three
| От | a.sokolov@postgrespro.ru |
|---|---|
| Тема | Re: On login trigger: take three |
| Дата | |
| Msg-id | 20798fcd14615193ce31005ca6c40ef2@postgrespro.ru обсуждение исходный текст |
| Ответ на | Re: On login trigger: take three (Daniel Gustafsson <daniel@yesql.se>) |
| Ответы |
Re: On login trigger: take three
|
| Список | pgsql-hackers |
Daniel Gustafsson писал 2022-03-22 11:43: >> On 22 Mar 2022, at 04:48, Andres Freund <andres@anarazel.de> wrote: > >> docs fail to build: >> https://cirrus-ci.com/task/5556234047717376?logs=docs_build#L349 > > Ugh, that one was on me and not the original author. Fixed. > + data initialization. It is vital that any event trigger using the + <literal>login</literal> event checks whether or not the database is in + recovery. Does any trigger really have to contain a pg_is_in_recovery() call? In this message (https://www.postgresql.org/message-id/20220312024652.lvgehszwke4hhove%40alap3.anarazel.de) it was only about triggers on hot standby, which run not read-only queries -- Andrey Sokolov Postgres Professional: http://www.postgrespro.com
В списке pgsql-hackers по дате отправления: