From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: when the startup process doesn't (logging startup delays) |
Date: | 2021-08-14 21:47:00 |
Message-ID: | 20210814214700.GO10479@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Should this feature distinguish between crash recovery and archive recovery on
a hot standby ? Otherwise the standby will display this all the time.
2021-08-14 16:13:33.139 CDT startup[11741] LOG: redo in progress, elapsed time: 124.42 s, current LSN: 0/EEE2100
If so, I think maybe you'd check !InArchiveRecovery (but until Robert finishes
cleanup of xlog.c variables, I can't say that with much confidence).
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-08-15 00:39:08 | Re: What are exactly bootstrap processes, auxiliary processes, standalone backends, normal backends(user sessions)? |
Previous Message | Tom Lane | 2021-08-14 15:23:00 | Re: Added schema level support for publication. |