public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Jim Ryan <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader
Date: Fri, 26 Jan 2018 11:35:09 -0700
Message-ID: <CAKFQuwajACsB5c1Ag1AsGoF5c2tkydtfdmzaDbB8xxOkrmaXHw@mail.gmail.com> (raw)
In-Reply-To: <CAOfX1iRaU7-PiA7tkHz5DL_LZMNsZZ5XA-AO6Fe+xLhzbUuQNw@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<CAOfX1iRaU7-PiA7tkHz5DL_LZMNsZZ5XA-AO6Fe+xLhzbUuQNw@mail.gmail.com>
On Friday, January 26, 2018, Jim Ryan <[email protected]> wrote:
> Hey Bruce,
>
> Thanks for working on this, but wouldn't pg_upgrade be needed from 10.1 to
> 10.2? Aren't those considered major versions, or am I misunderstanding?
>
> The source of my (and potentially others) confusion is if from 9.1 to 9.2
> is considered a major version change or not. I think most users would
> assume from 9.x to 10.x is a major version change. The ambiguity is in 9.x
> to 9.y.
>
>
Which is why we changed ;)
Starting with 10 the one and only value after the decimal is a minor
version bug fix release. The next major version will be 11.
Of versions beginning with 9 there were 7 major versions - 9.0 to 9.6; the
third position value denoted the minor bug fix release.
pg-upgrade is only required for upgrading between major versions.
On our homeoage we list every major release that is currently supported.
David J.
view thread (10+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader
In-Reply-To: <CAKFQuwajACsB5c1Ag1AsGoF5c2tkydtfdmzaDbB8xxOkrmaXHw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox