X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 52DB23A4BC7 for ; Fri, 21 Jan 2005 16:37:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48196-01 for ; Fri, 21 Jan 2005 16:37:32 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id 31AFA3A4B2E for ; Fri, 21 Jan 2005 16:37:19 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1Cs1me-0003it-00; Fri, 21 Jan 2005 11:37:16 -0500 To: pgsql-general@postgresql.org Subject: Re: Restoring fscked up postgres 7.1 References: <10071638046.20050121153328@grafton.lv> <20050121153001.GC3749@svana.org> <12179534609.20050121174505@grafton.lv> In-Reply-To: <12179534609.20050121174505@grafton.lv> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 21 Jan 2005 11:37:15 -0500 Message-ID: <87651qagck.fsf@stark.xeocode.com> Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.056 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/1168 X-Sequence-Number: 72117 Kristaps Armanis writes: > Is there any solution? I think what you have to do is use pg_resetxlog with -x and a value just shy of 2^32. then pg_dump and restore into a fresh database. I've never done it though so perhaps you should wait until someone with more experience speaks up. I would also suggest taking a cold backup of the bad database before running pg_resetxlog. -- greg