| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "k(dot)jamison(at)fujitsu(dot)com" <k(dot)jamison(at)fujitsu(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: please update ps display for recovery checkpoint |
| Date: | 2020-12-08 17:00:44 |
| Message-ID: | 549f04f1-6362-b599-c5e6-87330e36f03d@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/12/05 2:17, Bossart, Nathan wrote:
> On 12/3/20, 1:19 PM, "Bossart, Nathan" <bossartn(at)amazon(dot)com> wrote:
>> I like the idea behind this patch. I wrote a new version with a
>> couple of changes:
>
> I missed an #include in this patch. Here's a new one with that fixed.
I agree it might be helpful to display something like "checkpointing" or "waiting for checkpoint" in PS title for the startup process.
But, at least for me, it seems strange to display "idle" only for checkpointer. *If* we want to monitor the current status of checkpointer, it should be shown as wait event in pg_stat_activity, instead?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bossart, Nathan | 2020-12-08 17:29:30 | Re: Change default of checkpoint_completion_target |
| Previous Message | Vik Fearing | 2020-12-08 16:33:55 | Re: SEARCH and CYCLE clauses |