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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Sergey Dudoladov <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-31 07:41:57
Message-ID: CALj2ACXWAf4p3GQU84dJUmf+WYtrMOwiQnUTk3dUCYNwJWP_Bg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 31, 2022 at 12:47 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Jan 31, 2022 at 01:54:16PM +0800, Julien Rouhaud wrote:
> > For now we have some room, but we will likely keep consuming bytes in that file
> > for more critical features and it's almost certain that at one point we will
> > regret wasting 2 bytes for that.
>
> Agreed to drop the patch. That's only two bytes, but we may regret
> that in the future and this is not critical for the system.

I agree. Thank you all for your review.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-01-31 07:57:13 Re: Catalog version access
Previous Message Amit Kapila 2022-01-31 07:38:11 Re: row filtering for logical replication