Re: PostgreSQL 13 RC 1 release announcement draft - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostgreSQL 13 RC 1 release announcement draft
Date
Msg-id 1489075.1600264352@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL 13 RC 1 release announcement draft  (Magnus Hagander <magnus@hagander.net>)
Responses Re: PostgreSQL 13 RC 1 release announcement draft  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Wed, Sep 16, 2020 at 2:34 PM Jonathan S. Katz <jkatz@postgresql.org>
> wrote:
>> We've typically recommended doing the pg_upgrade since they may be
>> coming from a version with a lower catversion. I can change "you will
>> need" to "you may need" to be more accurate, but then that leads to the
>> question "who may need?".

>  Maybe something like:

> To upgrade from beta <when was the last catversion change>, you will need
> to use a major version upgrade strategy..... To upgrade from beta <when
> there was no catversion change>, just installing the new version and
> restarting PostgreSQL is enough.

The last catversion bump was between beta2 and beta3.  Thus, if you
were using beta2 or earlier, you *will* need a pg_upgrade or whatever.
If you were on beta3 then it's more like a minor upgrade, just install
the release executables and go.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Avoid useless retrieval of defaults and check constraints in pg_dump -a
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL 13 RC 1 release announcement draft