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

From Alvaro Herrera
Subject Re: oldest/newestCommitTs output by pg_controldata
Date
Msg-id 20151228183035.GL58441@alvherre.pgsql
Whole thread Raw
In response to Re: oldest/newestCommitTs output by pg_controldata  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: oldest/newestCommitTs output by pg_controldata
List pgsql-hackers
Tom Lane wrote:
> Joe Conway <mail@joeconway.com> writes:
> > I think the attached does the job. Note I settled on
> > (new|old)estCommitTsXid as that seemed most descriptive and not horribly
> > longer than before. It did mean, however, that I needed to add a single
> > space to all the output in pg_resetxlog and pg_controldata, which added
> > a fair amount to the patch size.
> 
> Hm.  That will break all the translations for those messages, no?
> Not sure it's worth it.

Yeah, I would leave the others alone and just let this line have the
value shifted one more column to the right.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: oldest/newestCommitTs output by pg_controldata
Next
From: Alvaro Herrera
Date:
Subject: Re: 9.5rc1 brin_summarize_new_values