Re: Open 7.3 issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Open 7.3 issues
Date: 2002-08-16 16:34:25
Message-ID: 8613.1029515665@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I hadn't looked at flags yet. Thomas's concern, and I think a valid
> one, is that if we move it from contrib into the main tree, people may
> accidentally run pg_resetxlog without understanding the issues involved.

There's already an interlock to prevent you from running it against a
live installation (it won't run if it sees a postmaster lock file).
That should also prevent an accidental run against a crashed installation
(presumably a lockfile will still be there). And if you run it against
a cleanly-shut-down installation, it's harmless because you don't need
the old xlog.

I don't think we need to be so paranoid as to insist that you say
pg_resetxlog --yes-i-read-the-manual
before it will do anything.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-16 16:40:02 Re: where to put NO_MKTIME_BEFORE_1970?
Previous Message Tom Lane 2002-08-16 16:27:12 Re: Admin nice-to-have's