| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | sergey(dot)dudoladov(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, tomas(dot)vondra(at)enterprisedb(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com |
| Subject: | Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint? |
| Date: | 2022-01-28 02:00:46 |
| Message-ID: | 20220128020046.6nq55y4jo6wysiqt@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Fri, Jan 28, 2022 at 10:38:53AM +0900, Kyotaro Horiguchi wrote:
>
> I'd like to see the PID of the triggering process, but it is really
> not a information suitable in the control file...
Yes that's something I would like too. But even if the PIDs could be store, I
don't think that having the information for an already completed checkpoint
would be of any use at all.
For the current checkpoint, it should also be an array of PID. For instance if
the checkpointer started a throttled checkpoint, then someone calls a non
immediate pg_start_backup() and finally thinks it's too slow and need a fast
checkpoint. This would be welcome in a new pg_stat_progress_checkpoint view.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-01-28 02:10:36 | Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint? |
| Previous Message | Thomas Munro | 2022-01-28 01:48:58 | Re: Creation of an empty table is not fsync'd at checkpoint |