"Jonathan S. Katz" writes:
> My inclination is to leave the statement alone or use that 2nd proposal
> I listed upthread.
I'd go with the simplest wording. As you say, people running betas
are probably sufficiently versed in what to do that they don't need
the release announcement to tell them.
On 9/16/20 9:52 AM, Tom Lane wrote:
> Magnus Hagander writes:
>> On Wed, Sep 16, 2020 at 2:34 PM Jonathan S. Katz
>> 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"
Magnus Hagander writes:
> On Wed, Sep 16, 2020 at 2:34 PM Jonathan S. Katz
> 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
On Wed, Sep 16, 2020 at 2:34 PM Jonathan S. Katz
wrote:
> On 9/16/20 1:08 AM, Peter Eisentraut wrote:
> > On 2020-09-15 18:10, Jonathan S. Katz wrote:
> >> To upgrade to PostgreSQL 13 RC 1 from Beta 3 or an earlier version of
> >> PostgreSQL 13, you will need to use a strategy similar to
On 9/16/20 1:08 AM, Peter Eisentraut wrote:
> On 2020-09-15 18:10, Jonathan S. Katz wrote:
>> To upgrade to PostgreSQL 13 RC 1 from Beta 3 or an earlier version of
>> PostgreSQL 13, you will need to use a strategy similar to upgrading
>> between
>> major versions of PostgreSQL (e.g. `pg_upgrade`
On 2020-09-15 18:10, Jonathan S. Katz wrote:
To upgrade to PostgreSQL 13 RC 1 from Beta 3 or an earlier version of
PostgreSQL 13, you will need to use a strategy similar to upgrading between
major versions of PostgreSQL (e.g. `pg_upgrade` or `pg_dump` / `pg_restore`).
Is this correct? I don't
Hi,
Attached is a draft of the PostgreSQL 13 RC 1 release announcement.
If you have feedback, please be sure you've left it no later than
2020-09-16 AoE.
Thanks!
Jonathan
PostgreSQL 13 RC 1 Released
===
The PostgreSQL Global Development Group announces that the first
