pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: Migration from 7.1.3. to 7.4.7.
Date: Mon, 21 Mar 2005 14:56:30 -0500
Message-ID: <60wts0u61d.fsf@dba2.int.libertyrms.com> (raw)
References: <39qlrmF62i3vgU1@individual.net>
	<1111420428.26897.51.camel@state.g2switchworks.com>

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.



view thread (4+ messages)

Message-ID: <60wts0u61d.fsf@dba2.int.libertyrms.com>
Permalink:  ../60wts0u61d.fsf@dba2.int.libertyrms.com/
Also on:    postgresql.org/message-id/60wts0u61d.fsf@dba2.int.libertyrms.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Migration from 7.1.3. to 7.4.7.
  In-Reply-To: <60wts0u61d.fsf@dba2.int.libertyrms.com>
  References: <39qlrmF62i3vgU1@individual.net> <1111420428.26897.51.camel@state.g2switchworks.com> <60wts0u61d.fsf@dba2.int.libertyrms.com>

* 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