public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thom Brown <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Dave Page <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: pg_upgrade invalid option
Date: Sat, 12 Jun 2010 18:43:10 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On 12 June 2010 18:15, Bruce Momjian <[email protected]> wrote:
> Thom Brown wrote:
>> >> The only options available are:
>> >>
>> > <snip>
>> >
>> >> Are those instructions for an older version?
>> >>
>> >
>> > That's Bruce's book which is probably 8 or 9 years old now. It's
>> > almost certainly referring to the old pg_upgrade shell script from
>> > years ago.
>> >
>>
>> Ah, unfortunately that's the first result in Google.  I've resorted to
>
> 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?

Thom

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pg_upgrade invalid option
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox