From: | Naomi Walker <nwalker(at)eldocomp(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Naomi Walker <nwalker(at)eldocomp(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Upgrade Information |
Date: | 2002-02-08 20:55:50 |
Message-ID: | 4.2.2.20020208135500.00ae6350@ecint.ecinet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
At 01:53 PM 2/8/02 -0500, Bruce Momjian wrote:
>Naomi Walker wrote:
> > We are currently using Postgresql 7.1.2, running on a E3500 server, OS
> > Solaris 2.6. We would like to upgrade to postgresql 7.2.
> >
> > 1) Do you all consider it stable enough now to upgrade?
> >
> > 2) If I understand correctly, to upgrade, step would be:
> >
> > a) pg_dumpall
> > b) reset PGHOME to new version of postgresql
> > c) pg_restore
> >
> > Is this correct?
> >
> > If so, that seems pretty drastic. I cannot imagine that once our
> databases
> > start getting really huge that this will last as an upgrade method. I
> > thought we would be using pg_upgrade, but I see a note that it will not
> > work with versions of postgres 7.1 and higher.
> >
> > Why did pg_upgrade go away, and can we look forward to one in the future?
>
>It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades,
>though it is only lightly tested.
Bruce, are you saying I can use /contrib/pg_upgrade for my 7.1.2 to 7.2
upgrade?
--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100 ext 242
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-02-08 21:07:39 | Re: Upgrade Information |
Previous Message | Bruce Momjian | 2002-02-08 18:53:41 | Re: Upgrade Information |