Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 218172E2D45 for ; Fri, 25 Jan 2008 17:14:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 41061-01 for ; Fri, 25 Jan 2008 17:14:05 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 492BD2E022D for ; Fri, 25 Jan 2008 17:14:08 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m0PLE7hb019120; Fri, 25 Jan 2008 16:14:07 -0500 (EST) To: Steven Rosenstein cc: pgsql-admin@postgresql.org Subject: Re: Recovering a database in danger of transaction wrap-around In-reply-to: References: <3757.1201288206@sss.pgh.pa.us> Comments: In-reply-to Steven Rosenstein message dated "Fri, 25 Jan 2008 15:46:01 -0500" Date: Fri, 25 Jan 2008 16:14:06 -0500 Message-ID: <19119.1201295646@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/254 X-Sequence-Number: 28028 Steven Rosenstein 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