Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 3D13B9FA103 for ; Wed, 15 Aug 2007 11:31:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 81650-08 for ; Wed, 15 Aug 2007 11:31:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 50C709F9FCD for ; Wed, 15 Aug 2007 11:30:48 -0300 (ADT) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1ILJtC-0001cb-7c for pgsql-admin@postgresql.org; Wed, 15 Aug 2007 16:30:26 +0200 Received: from pirus.securax.be ([213.16.46.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Aug 2007 16:30:26 +0200 Received: from milen by pirus.securax.be with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Aug 2007 16:30:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: "Milen A. Radev" Subject: Re: Migration Between Releases Date: Wed, 15 Aug 2007 17:30:09 +0300 Lines: 31 Message-ID: References: <044201c7df47$7baf3320$1f7ca8c0@ellacoya.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: pirus.securax.be User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <044201c7df47$7baf3320$1f7ca8c0@ellacoya.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/174 X-Sequence-Number: 26505 George Wilk написа: > Could someone clarify the database dump/restore requirement for postgres > upgrades between major releases? > > The online help chapter "23.5. Migration Between Releases" states that: > > > > As a general rule, the internal data storage format is subject to change > between major releases of PostgreSQL (where the number after the first dot > changes). This does not apply to different minor releases under the same > major release (where the number after the second dot changes); these always > have compatible storage formats. For example, releases 7.2.1, 7.3.2, and 7.4 > are not compatible, whereas 7.2.1 and 7.2.2 are. > > > > I thought that the major release was the first number in the versioning > schema, the second represented minor release, and the third would be the > maintenance release or revision number (i.e. 8.2.4). I need to understand > this better for the sake of writing install scripts for my own Solaris > packages. Originally, my scripts were checking for the difference in the > major release between the output of "postgres -version" and PG_VERSION file, > looking at the first module of the versioning schema (i.e. 8 in "8.2.4"). > Is this still true, or should I be checking the minor release as well? http://www.postgresql.org/support/versioning -- Milen A. Radev