From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: when the startup process doesn't |
Date: | 2021-04-21 18:43:30 |
Message-ID: | 792087.1619030610@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andres Freund (andres(at)anarazel(dot)de) wrote:
>> On 2021-04-20 14:56:58 -0400, Tom Lane wrote:
>>> I wonder though whether we really need authentication here. pg_ping
>>> already exposes whether the database is up, to anyone who can reach the
>>> postmaster port at all. Would it be so horrible if the "can't accept
>>> connections" error message included a detail about "recovery is X%
>>> done"?
>> Unfortunately I think something like a percentage is hard to calculate
>> right now.
> While it obviously wouldn't be exactly accurate, I wonder if we couldn't
> just look at the WAL files we have to reply and then guess that we'll go
> through about half of them before we reach the end..? I mean, wouldn't
> exactly be the first time that a percentage progress report wasn't
> completely accurate. :)
Or we could skip all the guessing and just print something like what
the startup process exposes in ps status, ie "currently processing
WAL file so-and-so".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ondřej Žižka | 2021-04-21 19:03:16 | Re: Synchronous commit behavior during network outage |
Previous Message | Stephen Frost | 2021-04-21 18:36:24 | Re: when the startup process doesn't |