public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Jim Ryan <[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: Sat, 27 Jan 2018 10:05:43 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwajACsB5c1Ag1AsGoF5c2tkydtfdmzaDbB8xxOkrmaXHw@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<CAOfX1iRaU7-PiA7tkHz5DL_LZMNsZZ5XA-AO6Fe+xLhzbUuQNw@mail.gmail.com>
<CAKFQuwajACsB5c1Ag1AsGoF5c2tkydtfdmzaDbB8xxOkrmaXHw@mail.gmail.com>
On Fri, Jan 26, 2018 at 11:35:09AM -0700, David G. Johnston wrote:
> 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.
I decided I needed to be more explicit about the major version numbers
so I have added major and minor examples for the 9.6.x series and 10.x
series releases. Patch attached.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
Attachments:
[text/x-diff] version.diff (1.3K, 2-version.diff)
download | inline diff:
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
new file mode 100644
index 055eac3..cf4550b
*** a/doc/src/sgml/ref/pgupgrade.sgml
--- b/doc/src/sgml/ref/pgupgrade.sgml
***************
*** 38,46 ****
<application>pg_upgrade</application> (formerly called <application>pg_migrator</application>) allows data
stored in <productname>PostgreSQL</productname> data files to be upgraded to a later <productname>PostgreSQL</productname>
major version without the data dump/reload typically required for
! major version upgrades, e.g. from 9.6.3 to the current major release
! of <productname>PostgreSQL</productname>. It is not required for minor version upgrades, e.g. from
! 9.6.2 to 9.6.3.
</para>
<para>
--- 38,46 ----
<application>pg_upgrade</application> (formerly called <application>pg_migrator</application>) allows data
stored in <productname>PostgreSQL</productname> data files to be upgraded to a later <productname>PostgreSQL</productname>
major version without the data dump/reload typically required for
! major version upgrades, e.g. from 9.5.8 to 9.6.4 or from 10.7 to 11.2.
! It is not required for minor version upgrades, e.g. from 9.6.2 to 9.6.3
! or from 10.1 to 10.2.
</para>
<para>
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: <[email protected]>
* 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