On Tue, Mar 8, 2022 at 8:31 PM Nitin Jadhav
<nitinjadhavpostgres@gmail.com> wrote:
>
> > > [local]:5432 ashu@postgres=# select * from pg_stat_progress_checkpoint;
> > > -[ RECORD 1 ]-----+-------------------------------------
> > > pid | 22043
> > > type | checkpoint
> > > kind | immediate force wait requested time
> > >
> > > I think the output in the kind column can be displayed as {immediate,
> > > force, wait, requested, time}. By the way these are all checkpoint
> > > flags so it is better to display it as checkpoint flags instead of
> > > checkpoint kind as mentioned in one of my previous comments.
> >
> > I will update in the next patch.
>
> The current format matches with the server log message for the
> checkpoint start in LogCheckpointStart(). Just to be consistent, I
> have not changed the code.
>
See below, how flags are shown in other sql functions like:
ashu@postgres=# select * from heap_tuple_infomask_flags(2304, 1);
raw_flags | combined_flags
-----------------------------------------+----------------
{HEAP_XMIN_COMMITTED,HEAP_XMAX_INVALID} | {}
(1 row)
This looks more readable and it's easy to understand for the
end-users.. Further comparing the way log messages are displayed with
the way sql functions display its output doesn't look like a right
comparison to me. Obviously both should show matching data but the way
it is shown doesn't need to be the same. In fact it is not in most of
the cases.
> I have taken care of the rest of the comments in v5 patch for which
> there was clarity.
>
Thank you very much. Will take a look at it later.
--
With Regards,
Ashutosh Sharma.