| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | a(dot)sokolov(at)postgrespro(dot)ru |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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 17:10:26 |
| Message-ID: | 20220328171026.o6vbs7c3o5lv45sm@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-28 15:57:37 +0300, a(dot)sokolov(at)postgrespro(dot)ru wrote:
> + 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?
Not *any* trigger, just any trigger that writes.
> 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
The problem precisely is that the login triggers run on hot standby nodes, and
that if they do writes, you can't login anymore.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Orlov | 2022-03-28 17:29:29 | Re: Assert in pageinspect with NULL pages |
| Previous Message | Robert Haas | 2022-03-28 16:57:02 | Re: multithreaded zstd backup compression for client and server |