Re: AWS forcing PG upgrade from v9.6 a disaster

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jan Wieck <jan(at)wi3ck(dot)info>, "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Date: 2021-05-28 21:30:52
Message-ID: 20210528213052.GC5649@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On Fri, May 28, 2021 at 05:15:33PM -0400, Andrew Dunstan wrote:
> > How did you load the database? pg_dump -> psql/pg_restore?
> >
> > If so, did you perform a VACUUM FREEZE after the load?
>
> Jan
>
>
> AIUI he did an RDS upgrade. Surely that's not doing a dump/restore? I
> assume you would know better than him or me what it actually does do :-)

I think it uses pg_upgrade.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bob Lunney 2021-05-28 22:09:50 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Andrew Dunstan 2021-05-28 21:15:33 Re: AWS forcing PG upgrade from v9.6 a disaster

Browse pgsql-performance by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2021-05-28 22:06:10 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Andrew Dunstan 2021-05-28 21:15:33 Re: AWS forcing PG upgrade from v9.6 a disaster