From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Upgrading from 11 to 13 |
Date: | 2021-03-30 19:31:27 |
Message-ID: | eaaef2a6-7d20-511d-2269-689f5293263e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/30/21 10:51 AM, Ron wrote:
> On 3/30/21 9:53 AM, Daniel Westermann (DWE) wrote:
>>> On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote:
>>>> Hi,
>>>>
>>>> Le mar. 30 mars 2021 à 16:10, Susan Joseph <sandajoseph(at)verizon(dot)net>
>>>> a écrit :
>>>>
>>>> I am currently using PostgreSQL 11.2 and would like to try and
>>>> upgrade it
>>>> to the latest version 13. Can I go straight from 11 to 13 or
>>>> do I need to
>>>> upgrade to 12 first and then to 13?
>>>>
>>>>
>>>> You can go straight to 13.
>>> We get this question often. Why do people feel they need to upgrade to
>>> intermediate releases? If we knew, maybe we could better clarify this.
>> I believe this is coming from the Oracle world. You can, e.g.not
>> directly go from 9 to18. There are supported upgrade paths and you
>> need to stick to those, but they are documented.
>
> Not even Postgresql allows you to jump from ancient versions to the most
> modern version. (No competent system makes you upgrade to the very next
> major version...)
>
pg_dump version 10+ will dump versions back to 8.0. pg_dump 9.6 reaches
back to version 7.0. So it is possible to upgrade from old versions in
one leap, whether it is advisable is another question.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2021-03-30 19:36:16 | Re: = t1 - t0 but t0 + i <> t1 when t1 and t2 timestamptz values and i is an interval value |
Previous Message | Tom Lane | 2021-03-30 18:46:21 | Re: Debugging leaking memory in Postgresql 13.2/Postgis 3.1 |