Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 603199F9D8E for ; Wed, 15 Aug 2007 11:21:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 74219-02 for ; Wed, 15 Aug 2007 11:20:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by postgresql.org (Postfix) with ESMTP id 413F29F9D50 for ; Wed, 15 Aug 2007 11:20:55 -0300 (ADT) Received: from YZANGXP ([192.168.124.31]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 15 Aug 2007 10:20:54 -0400 From: "George Wilk" To: Subject: Migration Between Releases Date: Wed, 15 Aug 2007 10:20:51 -0400 Message-ID: <044201c7df47$7baf3320$1f7ca8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0443_01C7DF25.F49D9320" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: AcffR3uEVb09NBdbSPiRtPEwKsZ9bg== X-OriginalArrivalTime: 15 Aug 2007 14:20:54.0157 (UTC) FILETIME=[7D525BD0:01C7DF47] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1021-15364.000 X-TM-AS-Result: No--11.676400-4.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/173 X-Sequence-Number: 26504 This is a multi-part message in MIME format. ------=_NextPart_000_0443_01C7DF25.F49D9320 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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? Thanks in advance, ~george ------=_NextPart_000_0443_01C7DF25.F49D9320 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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?

 

Thanks in advance,

~george

------=_NextPart_000_0443_01C7DF25.F49D9320--