Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 397E563252A for ; Sat, 12 Jun 2010 14:59:00 -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 89650-05 for ; Sat, 12 Jun 2010 17:58:52 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ww0-f46.google.com (mail-ww0-f46.google.com [74.125.82.46]) by mail.postgresql.org (Postfix) with ESMTP id B91ED632731 for ; Sat, 12 Jun 2010 14:58:52 -0300 (ADT) Received: by wwb18 with SMTP id 18so2151642wwb.19 for ; Sat, 12 Jun 2010 10:58:51 -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=J5Q3lewOFmMEzi6x4s5QFDILx/ZfOOwcWBDe+bJwnaw=; b=VpppCLIjQIV+iHtdNL1gJxeKZz6BCEIGcsdDT6j4iB9RwRCxqHu9P8tZlhjRxrTxB8 JaSWG2k7xBlSW/421KmfzPBX2XIwZGtfr5GRq6Mu3xCmb40Ox+SBmX/oYIhTt/g6XmdR 91b1QRusJZp1MVoBeQ0dQwwa++FQrcQx3IGRM= 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=LjhYk+c6yVHQzBNiRvG61x4A8rIDK/r7l5OedOeTq+jpgzLrH1yDqId7Q6zecJcqWH qD2kdtMaSNUw7mLkq9VMJZBzmhsKcfOSl6JmOJhGE7DsTpt5XNUpXaFRn7PUeOruRf0Y R4MPRy3vTyFqIf9e0mMVwDBbYw8cxIoAbs0uM= Received: by 10.216.90.15 with SMTP id d15mr607276wef.0.1276365531169; Sat, 12 Jun 2010 10:58:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.188.209 with HTTP; Sat, 12 Jun 2010 10:58:31 -0700 (PDT) In-Reply-To: <201006121746.o5CHkYU28069@momjian.us> References: <201006121746.o5CHkYU28069@momjian.us> From: Thom Brown Date: Sat, 12 Jun 2010 18:58:31 +0100 Message-ID: Subject: Re: pg_upgrade invalid option To: Bruce Momjian Cc: Dave Page , pgsql-docs 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=-0.5 tagged_above=-5 required=5 tests=BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/24 X-Sequence-Number: 5592 On 12 June 2010 18:46, Bruce Momjian wrote: > 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 curren= t major >> > ? ? ? ?release of PostgreSQL, including snapshot and alpha releases. >> > >> > In fact, we were hoping people would test pg_upgrade during the requir= ed >> > 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. =A0I talks about renaming the ol= d > directory before installing the new installation, if necessary. > Ah, I see. Unfortunately it still wouldn't have helped since I had already installed the new beta. Normally it installs versions in parallel, but not in this case. :/ Had I planned it before installation, I would have ensured the binaries were moved beforehand. Nevermind. :) Thom