Re: Nicer error when connecting to standby with hot_standby=off

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, James Coleman <jtc331(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, David Steele <david(at)pgmasters(dot)net>, David Zhang <david(dot)zhang(at)highgo(dot)ca>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Nicer error when connecting to standby with hot_standby=off
Date: 2021-03-23 20:59:57
Message-ID: 1010835.1616533197@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> FATAL: the database system is starting up
> DETAIL: WAL is being applied to recover from a system crash.
> or
> DETAIL: The system is applying WAL to recover from a system crash.
> or
> DETAIL: The startup process is applying WAL to recover from a system crash.

I don't think the postmaster has enough context to know if that's
actually true. It just launches the startup process and waits for
results. If somebody saw this during a normal (non-crash) startup,
they'd be justifiably alarmed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-03-23 21:53:45 Re: Add client connection check during the execution of the query
Previous Message Tom Lane 2021-03-23 20:55:50 Re: pg_upgrade failing for 200+ million Large Objects