| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 13 RC 1 release announcement draft |
| Date: | 2020-09-16 13:52:32 |
| Message-ID: | 1489075.1600264352@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, Sep 16, 2020 at 2:34 PM Jonathan S. Katz <jkatz(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2020-09-16 14:05:43 | Re: PostgreSQL 13 RC 1 release announcement draft |
| Previous Message | Julien Rouhaud | 2020-09-16 13:34:12 | Re: Avoid useless retrieval of defaults and check constraints in pg_dump -a |