pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Milen A. Radev <milen@radev.net>
To: pgsql-admin@postgresql.org
Subject: Re: Migration Between Releases
Date: Wed, 15 Aug 2007 17:30:09 +0300
Message-ID: <f9v2li$1hl$1@sea.gmane.org> (raw)
In-Reply-To: <044201c7df47$7baf3320$1f7ca8c0@ellacoya.com>
References: <044201c7df47$7baf3320$1f7ca8c0@ellacoya.com>

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




view thread (9+ messages)  latest in thread

Message-ID: <f9v2li$1hl$1@sea.gmane.org>
Permalink:  ../f9v2li$1hl$1@sea.gmane.org/
Also on:    postgresql.org/message-id/f9v2li$1hl$1@sea.gmane.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: milen@radev.net
  Subject: Re: Migration Between Releases
  In-Reply-To: <f9v2li$1hl$1@sea.gmane.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox