From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201006121746.o5CHkYU28069@momjian.us>
Subject: Re: pg_upgrade invalid option
In-Reply-To: <AANLkTimYezMWdU0Z_iUE1sT0BZbPYF0X4sjLPrDZIROj@mail.gmail.com>
To: Thom Brown <thombrown@gmail.com>
Date: Sat, 12 Jun 2010 13:46:34 -0400 (EDT)
CC: Dave Page <dpage@pgadmin.org>, pgsql-docs <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Thom Brown wrote:
> > I am sure that will change soon. ?:-) ?The right URL is now #7 on
> > Google:
> >
> > ? ? ? ?http://developer.postgresql.org/pgdocs/postgres/pgupgrade.html
> >
> >> restoring from a full backup :( ?I don't think I could use it for
> >> upgrading from beta 1 to beta 2 anyway by the looks of things. ?The
> >> binary directories are updated since they share the same version
> >> number.
> >
> > You certainly could have. ?The docs say:
> >
> > ? ? ? ?F.31.1. Supported Versions
> >
> > ? ? ? ?pg_upgrade supports upgrades from 8.3.X and later to the current major
> > ? ? ? ?release of PostgreSQL, including snapshot and alpha releases.
> >
> > In fact, we were hoping people would test pg_upgrade during the required
> > beta2 catalog change.
> >
> 
> How would that work if the beta1 binaries are overwritten by the beta2
> binaries since they both share the same version number?

Uh, did you look at the URL I mentioned.  I talks about renaming the old
directory before installing the new installation, if necessary.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +