From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steven Rosenstein <srosenst@us.ibm.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Recovering a database in danger of transaction wrap-around
Date: Fri, 25 Jan 2008 16:14:06 -0500
Message-ID: <19119.1201295646@sss.pgh.pa.us> (raw)
In-Reply-To: <OF0106AD58.4DA91085-ON852573DB.0070DE7B-852573DB.007213D8@us.ibm.com>
References: <OF9BE59CFF.E7484997-ON852573DB.006729F4-852573DB.0067D0FC@us.ibm.com>
<3757.1201288206@sss.pgh.pa.us>
<OF0106AD58.4DA91085-ON852573DB.0070DE7B-852573DB.007213D8@us.ibm.com>
Steven Rosenstein <srosenst@us.ibm.com> writes:
> I used plain old VACUUM. Do you think VACUUM FULL might be faster or more
> effective?
No. I think you probably want to do a dump and reload, but first you
have to get past the anti-wraparound check.
One possibility I hadn't thought of before is to use a standalone
backend to increment the pg_database.datfrozenxid values by a few
thousand transactions. This would be a bad idea if you intended
to keep using the DB, but if you're just trying to get to a state
where you can run pg_dump, it seems acceptable.
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, srosenst@us.ibm.com
Subject: Re: Recovering a database in danger of transaction wrap-around
In-Reply-To: <19119.1201295646@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