Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint?

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: bharath(dot)rupireddyforpostgres(at)gmail(dot)com, sergey(dot)dudoladov(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, 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-31 03:40:15
Message-ID: 20220131034015.cvwg7l2lle4f6xg7@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Jan 31, 2022 at 11:10:45AM +0900, Kyotaro Horiguchi wrote:
>
> This means pg_controldata need to translate the flags into human-readable
> text but, to be clear, I still don't think its usefull in the control
> data.

I've been saying that since my first email, I also don't see any scenario where
having this specific information can be of any help.

Given Andres feedback, unless someone can provide some realistic use case I
think we should mark this patch as rejected and focus on a
pg_progress_checkpoint feature. I will do so in a couple of days when I will
close this commitfest.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-01-31 03:46:44 Re: DELETE CASCADE
Previous Message Dilip Kumar 2022-01-31 03:32:54 Re: [BUG]Update Toast data failure in logical replication