| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, sergey(dot)dudoladov(at)gmail(dot)com, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(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:47:39 |
| Message-ID: | CALj2ACVF5+z32jku8t98NPWmTcCn22JqGeKBPQZgtnnE+7w1rg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 28, 2022 at 7:30 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> 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.
Thanks all for the comments. pg_stat_progress_checkpoint is being
discussed in another thread [1].
I will respond to the other comments soon.
Regards,
Bharath Rupireddy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-01-28 02:54:49 | Re: substring odd behavior |
| Previous Message | Kyotaro Horiguchi | 2022-01-28 02:35:06 | Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint? |