Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id C119B6328CC
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sat, 12 Jun 2010 14:43:38 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 49603-04 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sat, 12 Jun 2010 17:43:31 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com
	[74.125.82.174])
	by mail.postgresql.org (Postfix) with ESMTP id 8CA426324C1
	for <pgsql-docs@postgresql.org>; Sat, 12 Jun 2010 14:43:31 -0300 (ADT)
Received: by wyb40 with SMTP id 40so2161530wyb.19
	for <pgsql-docs@postgresql.org>; Sat, 12 Jun 2010 10:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:mime-version:received:in-reply-to
	:references:from:date:message-id:subject:to:cc:content-type
	:content-transfer-encoding;
	bh=XTrQmTnNQKODTN2YGQfpu4eyNUcwfxJrsBOpe4woDbg=;
	b=sNfj/x5ga2JZNlacMRxeYk0oBhJxJuviiu3Sb8evjhZ1aXwau+lvyzoLPRdhfhuJ8U
	zzd9y8QStV0Q+cxh9/SYDKRpyg1Z0OI4usdjxQu95HofVkYLFNlfQfxcruJZtIgIbcN2
	MI8cr31az/wwB3RNr9lF+v9mhMMBxNcnW8g9w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=NW1uYuuejOvMWj7hTiYFS7yWPwdFGmPYMMaSXpRKbNtp9V3OcQWMLdCX+QMgBgTRMw
	dPOSQoongpS/EKwNXqjsNkV6jh6iyUDc590wtK0dx9J+NfNkexkRAm2RDEwSpoJ0MhxC
	avtvD86EAHEK3v4a0CgcRgvloYTrvlPCS+8AM=
Received: by 10.227.135.203 with SMTP id o11mr3452702wbt.229.1276364610182;
	Sat, 12 Jun 2010 10:43:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.188.209 with HTTP; Sat, 12 Jun 2010 10:43:10 -0700 (PDT)
In-Reply-To: <201006121715.o5CHFVv21596@momjian.us>
References: <AANLkTilLpicS1DnuN2mZkxaXoFfT-Jz5vzeoSXE2pPJS@mail.gmail.com>
	<201006121715.o5CHFVv21596@momjian.us>
From: Thom Brown <thombrown@gmail.com>
Date: Sat, 12 Jun 2010 18:43:10 +0100
Message-ID: <AANLkTimYezMWdU0Z_iUE1sT0BZbPYF0X4sjLPrDZIROj@mail.gmail.com>
Subject: Re: pg_upgrade invalid option
To: Bruce Momjian <bruce@momjian.us>
Cc: Dave Page <dpage@pgadmin.org>, pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	RCVD_IN_DNSWL_NONE=-0.0001
X-Spam-Level: 
X-Archive-Number: 201006/22
X-Sequence-Number: 5590

On 12 June 2010 18:15, Bruce Momjian <bruce@momjian.us> 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. =A0I've resorted to
>
> I am sure that will change soon. =A0:-) =A0The right URL is now #7 on
> Google:
>
> =A0 =A0 =A0 =A0http://developer.postgresql.org/pgdocs/postgres/pgupgrade.=
html
>
>> restoring from a full backup :( =A0I don't think I could use it for
>> upgrading from beta 1 to beta 2 anyway by the looks of things. =A0The
>> binary directories are updated since they share the same version
>> number.
>
> You certainly could have. =A0The docs say:
>
> =A0 =A0 =A0 =A0F.31.1. Supported Versions
>
> =A0 =A0 =A0 =A0pg_upgrade supports upgrades from 8.3.X and later to the c=
urrent major
> =A0 =A0 =A0 =A0release of PostgreSQL, including snapshot and alpha releas=
es.
>
> 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