RE: Upgd from 7.0 to 7.1

Yes, this is probably what I'll do.  My drive is at 36% right now, so I
should have enough.  I also like haveing a back-out plan...

Thanx,
Mike Diehl,
Network Monitoring Tool Devl.
Sandia National Laboratories.
(505) 284-3137
jdiehl@sandia.gov

> -----Original Message-----
> From: Thomas Swan [mailto:tswan-lst@ics.olemiss.edu]
> Sent: May 29, 2001 4:41 PM
> To: Diehl, Jeffrey
> Cc: pgsql-sql@postgresql.org
> Subject: Re: [SQL] Upgd from 7.0 to 7.1
> 
> 
> Jeffrey:
> 
> dump_all the old DB (with the current version of postgres running)
> stop the old postmaster
> copy that DB directory (ie /var/lib/pgsql) to an alternate location
> create a new directory for the location you want postgresql to run, 
> (i.e. the old location)
> check the permissions on it...
> start the new version of postgresql...
> do the import (as postgres) ...
> 
> I think that would be the best way to go about it.  It's a lot easier 
> than sorting out multiple postmasters, ports, etc...
> 
> If everything goes well, you should be up and running.  If 
> not, you can 
> restore the old directory and run the old backend...
> 
> Hope this helps...
> 
> Thomas
> 
> 
> 
> Diehl, Jeffrey wrote:
> 
> >I assume, then, that if I RTFM, I'll be able to figure out 
> how to run two
> >db's at the same time...  I guess I have to run them in different
> >directories?  Or, do I do a dumpall, start the new server and do the
> >restore? Which is the best method?
> >
> >Thanx,
> >Mike Diehl,
> >Network Monitoring Tool Devl.
> >Sandia National Laboratories.
> >(505) 284-3137
> >jdiehl@sandia.gov
> >
> 
> 
>