| From: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-05-28 20:33:18 |
| Message-ID: | 0da29d18-8864-3e31-e2aa-21277bce6bff@mailpen.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2021-05-28 20:37:41 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Jan Wieck | 2021-05-28 20:23:06 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2021-05-28 20:37:41 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Jan Wieck | 2021-05-28 20:23:06 | Re: AWS forcing PG upgrade from v9.6 a disaster |