Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ef8qJ-0004ls-12 for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 18:35:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ef8qI-00083X-IW for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 18:35:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ef8qI-00083M-DK for pgsql-docs@lists.postgresql.org; Fri, 26 Jan 2018 18:35:14 +0000 Received: from mail-qt0-x241.google.com ([2607:f8b0:400d:c0d::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ef8qF-0004UU-Mr for pgsql-docs@postgresql.org; Fri, 26 Jan 2018 18:35:13 +0000 Received: by mail-qt0-x241.google.com with SMTP id d54so3624195qtd.4 for ; Fri, 26 Jan 2018 10:35:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bSivHWo+c1EvYzHoYOxEKLHEGsW7YjHL7Qn/AsQv9dk=; b=CCwTKBiCXadF8gg83tttufSw9aaRi5OVjeRjToShPMLUMSnWPbSCPWA/eJJL6EQn89 b6w3IVcnycte5iBV/u4aqX9GtDtfcqhRDIj0YFzfbfy8LZz8hMrsLdATr1LQVS8Vf5Pp yOnJT4lTmMu91gCtQfb0MRNCWCM7sURIXQRT56R/D2OoRfz9l8bPffYKGBVwU6ayta12 yBQkuabEaWYCmvM+CXgNEXq9bQY/g+GB3aZItrSKZcEBP6t/gOKgeB3nncqmhh+q+bQ5 UyohBo8leICzJEtSlmgfDiHYif4+LNsmiR2UuLfhmFW7Hsu7G6lDbNlP6xQoPK5jLfZN Rk4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bSivHWo+c1EvYzHoYOxEKLHEGsW7YjHL7Qn/AsQv9dk=; b=VButb1KJsbz5tZCp5UEox8XUF1HHo9rke5nTZWY9tnp1Q95ZPCR+wb6oi2HP/u77i5 WBIT1WNGYkoiLeP7lH+aOWiiXLhFBanF/NMlBO5pXLd4F/iEQEUkaPprCiAHPDXoMZ/w zJq7eRH5uz2vlA5iKPG+7ZZuH4KJuDLrpPLcXpCkCRyB/dwK2z8FkNiTxffuBn5jQNmE RxtjLmyLwyPkPkZMON18DJOjijjI0VhHOuzqTKc8FuN3ll/hQe220+X/3Eh8ErYf7BfV xRfvc+eZfd9fWFb9cmE33Km4B5VA5ZRC+xy8m0IwMyuAtvm0gaOLmDKLDIyr6Zh0Me7Q kbow== X-Gm-Message-State: AKwxytesYyKHb2BkX/vAbK1az1yR1BC2jp137ffmpkc9bUpReTyD8XOL XLaI2gmdE5Udg4hRkJrN21PG+b9V3/8NLV7FNX4= X-Google-Smtp-Source: AH8x225xvDmJXsgk5SFVljxSfDAwhP1fhqyC/LeDahIVLmhXmj3c5pfqaYfYIeZ8KA/zpOBT/qnBN4wSgk8p7/AxpLQ= X-Received: by 10.200.38.13 with SMTP id u13mr24491715qtu.269.1516991710231; Fri, 26 Jan 2018 10:35:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.135.38 with HTTP; Fri, 26 Jan 2018 10:35:09 -0800 (PST) In-Reply-To: References: <20171218213041.25744.8414@wrigleys.postgresql.org> <20180126002618.GA20836@momjian.us> From: "David G. Johnston" Date: Fri, 26 Jan 2018 11:35:09 -0700 Message-ID: Subject: Re: pg_upgrade docs are confusing if PostgreSQL's versioning system/language isn't known to reader To: Jim Ryan Cc: Bruce Momjian , "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary="001a11406c5203ff6d0563b2289d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a11406c5203ff6d0563b2289d Content-Type: text/plain; charset="UTF-8" On Friday, January 26, 2018, Jim Ryan 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. --001a11406c5203ff6d0563b2289d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, January 26, 2018, Jim Ryan <jim@room118solutions.com> wrote:
Hey Bruce,

Thanks for working= on this, but wouldn't pg_upgrade be needed from 10.1 to 10.2?=C2=A0 Ar= en'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.=C2=A0 I think= most users would assume from 9.x to 10.x is a major version change.=C2=A0 = The ambiguity is in 9.x to 9.y.=C2=A0=C2=A0


Which is why we changed ;)

=
Starting with 10 the one and only value after the decimal is a minor v= ersion bug fix release.=C2=A0 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 majo= r versions.

On our homeoage we list every major re= lease that is currently supported.

David J.
--001a11406c5203ff6d0563b2289d--