Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 95E096339A6 for ; Wed, 24 Feb 2010 16:29:23 -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 76693-04-5 for ; Wed, 24 Feb 2010 20:29:12 +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 A91ED634511 for ; Wed, 24 Feb 2010 16:28:43 -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 1NkNqY-0006IH-Mn; Wed, 24 Feb 2010 12:28:40 -0800 Message-ID: <4B858BF6.2000509@agliodbs.com> Date: Wed, 24 Feb 2010 12:28:38 -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: Mario Splivalo , pgsql-testers@postgresql.org, IP Subject: Re: Postgres 9.0alpha4? References: <1632668331.8712801267042709133.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> In-Reply-To: <1632668331.8712801267042709133.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.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/15 X-Sequence-Number: 44 On 2/24/10 12:18 PM, Lou Picciano wrote: > Thanks, Josh, for the notes - these are helpful. I'm inferring from > them that a new instance build - from an 8.4-alpha - won't be necessary > for this one? Actually, we generally don't bother to make the catalog versions compatible for alphas; we assume that people are going to re-initdb on a new build. > The revision of the major version number is a bit misleading; per > previous renumbering conventions (dare I say conventions?), the v9 > family change would have suggested a major architectural difference. > IE, that an initdb would be required... That's one reason. The other reason is major feature changes which will change the deployment of PostgreSQL, especially when those features can be assumed to be not-quite-entirely-stable in the first release. "9.0" says "New replication technology, may have bugs, use extra testing". > PS - Really looking forward to the replication features. Already have > the SSL build in place. Yaaay. I look forward to you testing replication over SSL connections. --Josh Berkus