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>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: 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 14:12:02
Message-ID: 3D47F032.12F19116@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> Perhaps. At the time they were written they were just quick hacks for
> debugging, but we've seen them needed often enough that maybe they need
> to be promoted.

Yes. Bruce, do you want to do the honors? Should we consider renaming
them at the time of the move? (probably not, but it is the right time to
ask)

> I think the right thing is to guess from resetxlog's own locale
> environment. Properly documented, that at least provides a way to
> recover --- if the admin screws up, well, not much we can do.
> The timestamp type can be guessed from whatever pg_config data is
> compiled into pg_resetxlog.

Right. The locale guessing already happens as you suggest.

- Thomas

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Richard Tucker 2002-07-31 14:58:58 Patch for roll forward recovery (PITR)
Previous Message Tom Lane 2002-07-31 14:01:13 Re: int64 timestamp patch for contrib/pg_controldata