Re: Upgrading from 11 to 13

From: Koen De Groote <kdg(dot)dev(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(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 19:47:10
Message-ID: CAGbX52Hi2turSnwakDXMNQatyFQ=O27LCvDymA9BNi39waR7rg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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".

On Sat, Apr 3, 2021 at 8:50 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 4/3/21 10:37 AM, Koen De Groote wrote:
> > Yes that's it. Probably something to alert people to. If they have this
> > set up, they can't "just to straight to 13".
> >
>
> Yes you can. You run into the same issue going from 11 --> 12 --> 13,
> you would just hit it in a different portion of the process.
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2021-04-03 20:05:18 Re: Upgrading from 11 to 13
Previous Message Peter J. Holzer 2021-04-03 19:19:54 Re: Upgrading from 11 to 13