Re: oldest/newestCommitTs output by pg_controldata - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: oldest/newestCommitTs output by pg_controldata
Date
Msg-id CAB7nPqSCG3Qt8hQ6T04+jvvQcRXmY-O6tirAq5_TUVrWDyDNKw@mail.gmail.com
Whole thread Raw
In response to oldest/newestCommitTs output by pg_controldata  (Joe Conway <mail@joeconway.com>)
Responses Re: oldest/newestCommitTs output by pg_controldata  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
On Sun, Dec 27, 2015 at 10:08 AM, Joe Conway <mail@joeconway.com> wrote:
> In looking at the exposing pg_controldata as function patch again, it
> struck me that the following output seems wrong:
>
> --------------
> Latest checkpoint's oldestCommitTs:   20257
> Latest checkpoint's newestCommitTs:   84159
> --------------
>
> Those numbers are XIDs, not timestamps. Shouldn't we either emit the
> actual timestamps, or else rename those to oldest/newestCommitXID?

I recall from the commit_ts thread that Alvaro had some real need to
make those fields XIDs and not timestamps, so +1 for renaming that as
suggested.
-- 
Michael



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: WIP: Covering + unique indexes.
Next
From: Michael Paquier
Date:
Subject: Re: 9.5rc1 brin_summarize_new_values