| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Koen De Groote <kdg(dot)dev(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Susan Joseph <sandajoseph(at)verizon(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Jonathan Katz <jkatz(at)postgresql(dot)org> |
| Subject: | Re: Upgrading from 11 to 13 |
| Date: | 2021-04-03 20:17:14 |
| Message-ID: | 09fccee8-465c-4069-4c59-c9d68e6a7a55@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/3/21 12:47 PM, Koen De Groote wrote:
> If an upgrade process has a part where old functionality doesn't work
> anymore, or anything at all breaks, then it's not "you can just upgrade
> no problems".
>
Major versions are allowed to break compatibility, so there is always a
chance for issues. That is why reading the Release Notes for the first
release in a major version is important. In any case the changes are
cumulative, so jumping X.x --> Y.x --> Z.x is not going to be overall
different from the changes you would get from X.x --> Z.x.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2021-04-04 02:06:31 | Re: Is replacing transactions with CTE a good idea? |
| Previous Message | Bruce Momjian | 2021-04-03 20:05:18 | Re: Upgrading from 11 to 13 |