Re: int64 timestamp patch for contrib/pg_controldata - Mailing list pgsql-patches

From Thomas Lockhart
Subject Re: int64 timestamp patch for contrib/pg_controldata
Date
Msg-id 3D478DC2.A9893EAD@fourpalms.org
Whole thread Raw
In response to Re: int64 timestamp patch for contrib/pg_controldata  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: int64 timestamp patch for contrib/pg_controldata  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
> I had a note that pg_resetxlog needs to be fixed as well; have you
> looked at that?

Shouldn't pg_resetxlog and pg_controldata be brought into the main tree?
They are admin utilities which seem to be done in a style which would
fit in.

Or is there another strategy for providing these capabilities coming
Real Soon which would make these obsolete?

It does look like pg_resetxlog needs to be fixed up, but only if
controldata is lost as well as the WAL files. How dicy is it to guess at
a proper controldata file? Seems that the locale settings etc are not
reliably guessable from just the environment (no, there is no analogy
with the other current Hot Topic ;)

                  - Thomas

pgsql-patches by date:

Previous
From: sugita@sra.co.jp
Date:
Subject: Re: int64 timestamp patch for contrib/pg_controldata
Next
From: Tom Lane
Date:
Subject: Re: int64 timestamp patch for contrib/pg_controldata