Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 6BEDC6339D3 for ; Tue, 3 Nov 2009 19:27:17 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 21629-09 for ; Tue, 3 Nov 2009 23:27:00 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id BB980633931 for ; Tue, 3 Nov 2009 19:27:06 -0400 (AST) Received: from dsl081-245-111.sfo1.dsl.speakeasy.net ([64.81.245.111] helo=Sidney-Stratton.local) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1N5SmB-0000bc-Gd; Tue, 03 Nov 2009 15:27:02 -0800 Message-ID: <4AF0BC42.3000905@agliodbs.com> Date: Tue, 03 Nov 2009 15:26:58 -0800 From: Josh Berkus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: Lou Picciano CC: pgsql-testers@postgresql.org, Greg Smith Subject: Re: alpha2 initdb PG_CONTROL_VERSION incompatibility? References: <329060923.6534111257290612647.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> In-Reply-To: <329060923.6534111257290612647.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.395 tagged_above=-10 required=5 tests=AWL=0.204, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/4 X-Sequence-Number: 9 Lou, > 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) Oh, I don't think there's been any attempt to tell alpha2 that it can accept an alpha1 InitDB. You have to re-initdb with each alpha. We're still making catalog changes. --Josh Berkus