Re: Upgd from 7.0 to 7.1

From: Thomas Swan <tswan-lst(at)ics(dot)olemiss(dot)edu>
To: "Diehl, Jeffrey" <jdiehl(at)sandia(dot)gov>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Upgd from 7.0 to 7.1
Date: 2001-05-29 22:41:19
Message-ID: 3B14258F.60906@ics.olemiss.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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(at)sandia(dot)gov
>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Diehl, Jeffrey 2001-05-29 22:43:12 RE: Upgd from 7.0 to 7.1
Previous Message Tom Lane 2001-05-29 22:37:54 Re: Slow inserts/deletes