Re: Upgrading from 11 to 13 - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Upgrading from 11 to 13
Date
Msg-id eaaef2a6-7d20-511d-2269-689f5293263e@aklaver.com
Whole thread Raw
In response to Re: Upgrading from 11 to 13  (Ron <ronljohnsonjr@gmail.com>)
List 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@verizon.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.klaver@aklaver.com



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Debugging leaking memory in Postgresql 13.2/Postgis 3.1
Next
From: Adrian Klaver
Date:
Subject: Re: = t1 - t0 but t0 + i <> t1 when t1 and t2 timestamptz values and i is an interval value