| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Sergey Dudoladov <sergey(dot)dudoladov(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Bharath Rupireddy <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-27 11:09:29 |
| Message-ID: | 20220127110929.dbfc5ccvpnqfjxvn@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 27, 2022 at 06:56:57PM +0800, Julien Rouhaud wrote:
>
> What it's showing is the "currently ongoing checkpoint or last completed
> checkpoint" kind.
Ah after double checking I see it's storing the information *after* the
checkpoint completion, so it's indeed the last completed checkpoint. I'm not
sure how useful it can be, but ok.
> Also, it's only showing the initial triggering conditions of checkpoints.
> For instance, if a timed checkpoint is started and then a backend executes a
> "CHECKPOINT;", it will upgrade the ongoing checkpoint with additional flags but
> AFAICS those new flags won't be saved to the control file.
This one is still valid I think, it's only storing the initial flags and not
the possibly upgraded one in shmem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2022-01-27 11:18:37 | Re: RFC: Logging plan of the running query |
| Previous Message | Julien Rouhaud | 2022-01-27 10:56:57 | Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint? |