Horton

Re: please update ps display for recovery checkpoint

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Robert Haas <robertmhaas@gmail.com>
Cc: "Bossart, Nathan" <bossartn@amazon.com>, Justin Pryzby <pryzby@telsasoft.com>, Fujii Masao <masao.fujii@oss.nttdata.com>, "k.jamison@fujitsu.com" <k.jamison@fujitsu.com>, Thomas Munro <thomas.munro@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Nitin Jadhav <nitinjadhavpostgres@gmail.com>
Date: 2021-06-10T01:32:30Z
Lists: pgsql-hackers 
On Mon, Jun 07, 2021 at 01:28:06PM -0400, Robert Haas wrote:
> On Mon, Jun 7, 2021 at 12:02 PM Bossart, Nathan <bossartn@amazon.com> wrote:
>> 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.

+1.  I also agree with doing something for the ps output of the
startup process when these are happening in crash recovery.

> See also the nearby thread entitled "when the startup process doesn't"
> which touches on this same issue.

Here is a link to the thread:
https://www.postgresql.org/message-id/CA+TgmoaHQrgDFOBwgY16XCoMtXxsrVGFB2jNCvb7-ubuEe1MGg@mail.gmail.com
--
Michael

Commits

  1. Provide recovery_init_sync_method=syncfs.

  2. Add some checkpoint/restartpoint status to ps display