Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id B5E73636794
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sat, 12 Jun 2010 14:15:47 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 52476-07-2 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sat, 12 Jun 2010 17:15:40 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from momjian.us (momjian.us [70.90.9.53])
	by mail.postgresql.org (Postfix) with ESMTP id 27090634E17
	for <pgsql-docs@postgresql.org>; Sat, 12 Jun 2010 14:15:34 -0300 (ADT)
Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id
 o5CHFVv21596;
	Sat, 12 Jun 2010 13:15:31 -0400 (EDT)
From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201006121715.o5CHFVv21596@momjian.us>
Subject: Re: pg_upgrade invalid option
In-Reply-To: <AANLkTilLpicS1DnuN2mZkxaXoFfT-Jz5vzeoSXE2pPJS@mail.gmail.com>
To: Thom Brown <thombrown@gmail.com>
Date: Sat, 12 Jun 2010 13:15:31 -0400 (EDT)
CC: Dave Page <dpage@pgadmin.org>, pgsql-docs <pgsql-docs@postgresql.org>
X-Mailer: ELM [version 2.4ME+ PL124 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201006/21
X-Sequence-Number: 5589

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.

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

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