Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 57C0B6347EC for ; Wed, 24 Feb 2010 16:27:09 -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 76533-05-6 for ; Wed, 24 Feb 2010 20:26:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.postgresql.org (Postfix) with ESMTP id 4A9E5633222 for ; Wed, 24 Feb 2010 16:26:49 -0400 (AST) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Mc8Rz-1O1E952Yqt-00JCjh; Wed, 24 Feb 2010 21:26:47 +0100 Message-ID: <4B858B83.1070603@2ndquadrant.com> Date: Wed, 24 Feb 2010 15:26:43 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Lou Picciano CC: Josh Berkus , 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; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX192KxF/9NNpQdf6mr1pZ3Sm9pOrTrxdp0iM32B jElmkS5K5JNFT3bLERRPN6rvMcQJfYAW/eR9Ie6F1XfpNC3SwQ FX1n6BuqxFRyS0Ugy+njKGm6kmpAEz9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.185 tagged_above=-10 required=5 tests=BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201002/14 X-Sequence-Number: 43 Lou Picciano wrote: > > 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... There are major architectural differences internally and externally--the streaming replication implementation being the main one prompting the major version number bump, removal of the old way of doing VACUUM FULL is one of the big internal ones--and an initdb is required. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us