Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5FB21633F51 for ; Tue, 3 Nov 2009 19:34:17 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 42904-09 for ; Tue, 3 Nov 2009 23:34:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by mail.postgresql.org (Postfix) with ESMTP id 8B558633DC6 for ; Tue, 3 Nov 2009 19:34:09 -0400 (AST) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id nA3NY5Sx023703; Tue, 3 Nov 2009 18:34:05 -0500 (EST) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id nA3NY4Tt023699; Tue, 3 Nov 2009 18:34:04 -0500 (EST) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Tue, 3 Nov 2009 18:34:04 -0500 (EST) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Lou Picciano cc: pgsql-testers Subject: Re: alpha2 initdb PG_CONTROL_VERSION incompatibility? In-Reply-To: <329060923.6534111257290612647.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Message-ID: References: <329060923.6534111257290612647.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> User-Agent: Alpine 2.01 (GSO 1184 2008-12-16) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/5 X-Sequence-Number: 10 On Tue, 3 Nov 2009, Lou Picciano wrote: > The start command we're testing with, for example (the only variable is > datapath: data-NEW vs. data-OLD): > # /usr/local/postgres/8.5-alpha2/bin/pg_ctl -D > /var/postgres/8.5-alpha2/data-NEW -l /var/postgres/8.5-alpha2/TEMPLOG start > (above works great, with an alpha2-init'd data cluster) OK, the original message you sent suggested this didn't work either which was the confusing part. The fact that you have to do a fresh initdb to go from anything earlier to alpha2 is expected. The fact that you could go from 8.4 to 8.5-alpha just reflects that nobody made any internal changes to the database layout between those versions. That it worked was a lucky oddity, what you're seeing now is the more common situation. In general, you have to do a fresh initdb for each testing release to make a database cluster that the new code will talk to. That this changes each sub-release is one reason these are strictly useful as test releases. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD