Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1C25B63353A for ; Tue, 3 Nov 2009 23:45:50 -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 65654-03 for ; Wed, 4 Nov 2009 03:45:30 +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 7041663222F for ; Tue, 3 Nov 2009 23:45:39 -0400 (AST) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id nA43jLdr004803; Tue, 3 Nov 2009 22:45:21 -0500 (EST) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id nA43jL6Y004799; Tue, 3 Nov 2009 22:45:21 -0500 (EST) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Tue, 3 Nov 2009 22:45:21 -0500 (EST) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Lou Picciano cc: pgsql-testers@postgresql.org, Josh Berkus Subject: Re: alpha2 initdb PG_CONTROL_VERSION incompatibility? In-Reply-To: <1420936581.6647451257302990053.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Message-ID: References: <1420936581.6647451257302990053.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> User-Agent: Alpine 2.01 (GSO 1184 2008-12-16) MIME-Version: 1.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.509 tagged_above=-10 required=5 tests=AWL=0.090, BAYES_00=-2.599 X-Spam-Level: Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT X-Archive-Number: 200911/7 X-Sequence-Number: 12 On Wed, 4 Nov 2009, Lou Picciano wrote: > Is it just that the PG_CONTROL_VERSIONs don't follow the binary > numbering, and this point I simply haven't run into before? They match on official releases, but nobody worried about that detail for the first 8.5 alpha. It's basically impossible for an official release to make it all the way out the door without *something* causing a "catalog version bump", the thing that causes that number to be updated so the first couple of digits look right. There just didn't happen to be any such changes between the 8.4 release and the first 8.5 alpha. > > We're still making catalog changes. > PS -  (Are you both speaking here - 'we' - as authors of PostgreSQL?) That's specifically "we" as in "everyone who authors a change commited to PostgreSQL", which essentially includes everyone who might submit a patch. The committers have very strict rules for making changes to this version number during the course of official releases because it causes your old database installation to be incompatible (summary: don't do that; it has happened extremely rarely to fix serious bugs). This treadmill where you have to keep running initdb is essentially limited to pre-release testing, those who build regularly from CVS snapshots have to do this all the time. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD