From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade invalid option |
Date: | 2010-06-12 17:46:34 |
Message-ID: | 201006121746.o5CHkYU28069@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-06-12 17:58:31 | Re: pg_upgrade invalid option |
Previous Message | Thom Brown | 2010-06-12 17:43:10 | Re: pg_upgrade invalid option |