From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bill Bartlett <bbartlett@softwareanalytics.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PG 8.0.4 - Does Dump + drop_db + reload reset XID to prevent wraparound?
Date: Sat, 21 Jun 2008 11:25:25 -0400
Message-ID: <18778.1214061925@sss.pgh.pa.us> (raw)
In-Reply-To: <001401c8d388$4b5d0720$e2171560$@com>
References: <001401c8d388$4b5d0720$e2171560$@com>
"Bill Bartlett" <bbartlett@softwareanalytics.com> writes:
> In a PostgreSQL 8.0.4 environment, does dropping the database and
> reloading it completely reset the XID information that causes
> transaction ID wraparound?
I gather from the reference to "d:" that you're running on Windows.
You really, really, really need to put an urgent priority on getting
off 8.0.x. (Or get off Windows, but I suppose I'm wasting my breath
suggesting that.) The rename problem that you're hitting is fixed in
8.2 and up, as are a bunch of other Windows-specific problems that
will never be fixed in pre-8.2 branches, because we have abandoned
support for those branches on Windows.
As for the specific question, I think it'd work as long as template0
has never been unfrozen, but an initdb would be a lot more certain
--- and since you apparently have only one user database, there's
no difference in how much reload work you'd have to do.
Lastly, there is no need to use VACUUM FULL for wraparound protection;
plain VACUUM is sufficient. The critical point though is that it has
to be a database-wide VACUUM (and done by a superuser); 8.0 doesn't
track this at a per-table grain, only per-database.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, bbartlett@softwareanalytics.com
Subject: Re: PG 8.0.4 - Does Dump + drop_db + reload reset XID to prevent wraparound?
In-Reply-To: <18778.1214061925@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox