From: Dean Gibson (DB Administrator) <postgresql@mailpen.com>
To: pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: Fri, 28 May 2021 13:33:18 -0700
Message-ID: <0da29d18-8864-3e31-e2aa-21277bce6bff@mailpen.com> (raw)
In-Reply-To: <9fa75894-d3be-e40b-cd89-f641bdf85df0@dunslane.net>
References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com>
<9fa75894-d3be-e40b-cd89-f641bdf85df0@dunslane.net>
On 2021-05-28 12:08, Andrew Dunstan wrote:
> On 5/28/21 2:48 PM, Dean Gibson (DB Administrator) wrote:
>> [Reposted to the proper list]
>>
>> ...
>>
>>
>> Have you tried reproducing these results outside RDS, say on an EC2 instance running vanilla PostgreSQL?
>>
>> cheers, andrew
>>
>> --
>> Andrew Dunstan
>> EDB: https://www.enterprisedb.com
That is step #2 of my backup plan:
1. Create an EC2 instance running community v9.6. Once that is done
& running successfully, I'm golden for a long, long time.
2. If I am curious (& not worn out), take a snapshot of #1 & update it
to v13.
-- Dean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: postgresql@mailpen.com, pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
In-Reply-To: <0da29d18-8864-3e31-e2aa-21277bce6bff@mailpen.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox