Re: please update ps display for recovery checkpoint - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: please update ps display for recovery checkpoint
Date
Msg-id 32B59582-AA6C-4609-B08F-2256A271F7A5@amazon.com
Whole thread Raw
In response to Re: please update ps display for recovery checkpoint  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: please update ps display for recovery checkpoint  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 6/6/21, 7:14 PM, "Justin Pryzby" <pryzby@telsasoft.com> wrote:
> Now, I wonder whether the startup process should also include some detail about
> "syncing data dir".  It's possible to strace the process to see what it's
> doing, but most DBA would probably not know that, and it's helpful to know the
> status of recovery and what part of recovery is slow: sync, replay, or
> checkpoint.  commit df9274adf improved the situation between replay and
> ckpoint, but it's still not clear what "postgres: startup" means before replay
> starts.

I've seen a few functions cause lengthy startups, including
SyncDataDirectory() (for which I was grateful to see 61752afb),
StartupReorderBuffer(), and RemovePgTempFiles().  I like the idea of
adding additional information in the ps title, but I also think it is
worth exploring additional ways to improve on these O(n) startup
tasks.

Nathan


pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: SQL-standard function body
Next
From: Robert Haas
Date:
Subject: Re: please update ps display for recovery checkpoint