Re: please update ps display for recovery checkpoint

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: k(dot)jamison(at)fujitsu(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: please update ps display for recovery checkpoint
Date: 2020-10-02 09:13:54
Message-ID: 20201002091354.GH8476@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 02, 2020 at 04:28:14PM +0900, Michael Paquier wrote:
> > Related: I have always thought that this message meant "recovery will complete
> > Real Soon", but I now understand it to mean "beginning the recovery checkpoint,
> > which is flagged CHECKPOINT_IMMEDIATE" (and may take a long time).
>
> Yep. And at the end of crash recovery seconds feel like minutes.
>
> I agree that "checkpointer checkpoint" is not the best fit. Using
> parenthesis would also be inconsistent with the other usages of this
> API in the backend code.

I think maybe I got the idea for parenthesis from these:
src/backend/tcop/postgres.c: set_ps_display("idle in transaction (aborted)");
src/backend/postmaster/postmaster.c- if (port->remote_port[0] != '\0')
src/backend/postmaster/postmaster.c- appendStringInfo(&ps_data, "(%s)", port->remote_port);

> What about adding "running" then? This
> would give "checkpointer running end-of-recovery checkpoint".

What about one of these?
"checkpointer: running end-of-recovery checkpoint"
"checkpointer running: end-of-recovery checkpoint"

Thanks for looking.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tsunakawa.takay@fujitsu.com 2020-10-02 09:20:32 RE: Transactions involving multiple postgres foreign servers, take 2
Previous Message Fabien COELHO 2020-10-02 08:55:40 Re: pgbench - refactor init functions with buffers