X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1A62E5648D for ; Mon, 21 Mar 2005 20:12:12 +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 41619-03 for ; Mon, 21 Mar 2005 20:12:07 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id A8DA156478 for ; Mon, 21 Mar 2005 20:12:07 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j2LKC7Ia043321 for ; Mon, 21 Mar 2005 20:12:07 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j2LK5VmO040364 for pgsql-admin@postgresql.org; Mon, 21 Mar 2005 20:05:31 GMT (envelope-from news) From: Chris Browne X-Newsgroups: pgsql.admin Subject: Re: Migration from 7.1.3. to 7.4.7. Date: Mon, 21 Mar 2005 14:56:30 -0500 Organization: cbbrowne Computing Inc Lines: 39 Message-ID: <60wts0u61d.fsf@dba2.int.libertyrms.com> References: <39qlrmF62i3vgU1@individual.net> <1111420428.26897.51.camel@state.g2switchworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:u4vkI9sjJq01YW5KlXPLtXpl8nU= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/332 X-Sequence-Number: 16830 smarlowe@g2switchworks.com (Scott Marlowe) writes: > On Wed, 2005-03-16 at 06:07, Dr. Roger Wießner wrote: >> Can anyone tell me how to successfully migrate from 7.1.3. to 7.4.7.? I get >> lots of errors... > > Try to have both installed at once (separate dirs, or separate machines) > and dump the 7.1.3 db with the 7.4.7 pg_dump. You might want to do a > file system backup and an upgrade of 7.1.3 to the last version of 7.1.3. > > On rare occasions, an intermediate upgrade to something in between may > help, but I've not used 7.1 in a VERY long time. 7.1 is _mighty_ old, which gives a pretty considerable chance of there being data type changes that may break. I seem to recall doing an upgrade of some databases to 7.2 and discovering that the date type being used in the "ancient" version (which might well have been 6.5 or 7.0, even older than 7.1!) not existing in more modern versions. We wound up splitting the conversion into two pieces: - A schema conversion, where the types of fields were updated to those available in more modern versions. This is where most of the fiddling took place. - A data copy, where (if memory serves) we dumped the data as a set of INSERT statements rather than via COPY 'dumps'. Careful addition of BEGIN/COMMIT allowed the load to be acceptably fast, and the use of INSERT avoided differences between COPY formats... I'd do some "dry runs" (where you don't expect the results to necessarily be useful) to see what problems fall out. -- let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];; http://www.ntlug.org/~cbbrowne/linuxxian.html A VAX is virtually a computer, but not quite.