Re: pg_upgrade docs are confusing if PostgreSQL's versioningsystem/language isn't known to reader
| От | David G. Johnston |
|---|---|
| Тема | Re: pg_upgrade docs are confusing if PostgreSQL's versioningsystem/language isn't known to reader |
| Дата | |
| Msg-id | CAKFQuwajACsB5c1Ag1AsGoF5c2tkydtfdmzaDbB8xxOkrmaXHw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_upgrade docs are confusing if PostgreSQL's versioningsystem/language isn't known to reader (Jim Ryan <jim@room118solutions.com>) |
| Ответы |
Re: pg_upgrade docs are confusing if PostgreSQL's versioningsystem/language isn't known to reader
|
| Список | pgsql-docs |
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? 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.
В списке pgsql-docs по дате отправления: