Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 543439FB1DD for ; Wed, 29 Nov 2006 11:02:46 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 68086-01 for ; Wed, 29 Nov 2006 11:02:18 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from web31810.mail.mud.yahoo.com (web31810.mail.mud.yahoo.com [68.142.207.73]) by postgresql.org (Postfix) with SMTP id 7BF9B9F9EEF for ; Wed, 29 Nov 2006 11:02:36 -0400 (AST) Received: (qmail 43546 invoked by uid 60001); 29 Nov 2006 15:02:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Z9q1GH181Pf3iRoVsVb27MtcZDTVioh87I2BKzpLv4HDS4CL+HobQoHnZ0r1nbfCx1rOcKgMGUQBnCp4gJF7uVH7+fXfQjIzDBLxiRogLZ+Xx6q4LfEGXGFusXuoPX216AXSIP4CrlfraBRgvlgl7Pju/xS2EXLRRNVv83oWeBE=; X-YMail-OSG: uGm2pycVM1lqsgvOalxE5hNfgGC6lxbyXbvslAjpB.ee31cSaNvgcyiIXBl2uZldleexU21uchYJWrlldoEuMsHx5MPnA3.Q3tpVmyFAErBOLdootyiC7YFpEKfRCEALeN4AMxQw2EAt.F6naP6wZ8Ahla5dplK2Kg-- Received: from [12.177.97.50] by web31810.mail.mud.yahoo.com via HTTP; Wed, 29 Nov 2006 07:02:33 PST Date: Wed, 29 Nov 2006 07:02:33 -0800 (PST) From: Richard Broersma Jr Subject: Re: dump from 8.x restore to 7.3.x To: eddy@axa.it, pgsql-admin@postgresql.org In-Reply-To: <456D992A.90903@axa.it> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <475722.43429.qm@web31810.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.212 tagged_above=0 required=5 tests=AWL, BAYES_00, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS X-Spam-Level: X-Archive-Number: 200611/236 X-Sequence-Number: 23763 > We have a pretty big database that is going for an upgrade (PG7 -> PG8) > in the next few days, we have tested all the features of our application > but we cannot be sure that everything will work out perfectly (db is > managing several blob's only tables that have proven to be pretty hard > to configure). > I am currently investigating a worst-case-scenario strategy that would > be to downgrade the database from PG8 to 7 if anything goes wrong;00 > this implies that we: > 1) dump from a running PG8 > 2) remove PG8 and reinstall PG7 > 3) restore the dump into the running PG7 > > unfortunately pg_restore complains about the dump header and doesn't > restore the db at all, having tried to dump with both -Ft and -Fc flags > > shall I try the "--ignore-version" option in pg_restore? > is there going to be any problem in using this option? (corrupted data, > tables, etc.) My understanding is that dumps are not backwards compatible. Any dumps created with a Version 8.* pg_dump cannot be used for any older versions. If you want "play it safe" you should create a new server for the postgresql version 8.1 to preform validation tests with your front-ends. After you are satisfied that everything works well you can replace the version 7 production server with version 8. If you would like a safety net beyond this you could contact one of the PostgreSQL consulting companies to walk you through the integration of V.8.1 into your projection system. Regards, Richard Broersma Jr.