Skip site navigation (1) Skip section navigation (2)

Re: int64 timestamp patch for contrib/pg_controldata

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, sugita(at)sra(dot)co(dot)jp,pgsql-patches(at)postgresql(dot)org
Subject: Re: int64 timestamp patch for contrib/pg_controldata
Date: 2002-07-31 07:12:02
Message-ID: 3D478DC2.A9893EAD@fourpalms.org (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2002-07-31 14:01:13
Subject: Re: int64 timestamp patch for contrib/pg_controldata
Previous:From: sugitaDate: 2002-07-31 07:03:34
Subject: Re: int64 timestamp patch for contrib/pg_controldata

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group