From: | a(dot)sokolov(at)postgrespro(dot)ru |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, Ivan Panchenko <wao(at)mail(dot)ru>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Subject: | Re: On login trigger: take three |
Date: | 2022-03-28 12:57:37 |
Message-ID: | 20798fcd14615193ce31005ca6c40ef2@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Gustafsson писал 2022-03-22 11:43:
>> On 22 Mar 2022, at 04:48, Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2022-03-28 13:05:26 | Re: document the need to analyze partitioned tables |
Previous Message | Robert Haas | 2022-03-28 12:36:15 | Re: Add LZ4 compression in pg_dump |