| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-31 14:01:13 | Re: int64 timestamp patch for contrib/pg_controldata |
| Previous Message | sugita | 2002-07-31 07:03:34 | Re: int64 timestamp patch for contrib/pg_controldata |