Date: Fri, 28 May 2021 17:30:52 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jan Wieck <jan@wi3ck.info>,
	"Dean Gibson (DB Administrator)" <postgresql@mailpen.com>,
	pgsql-performance@lists.postgresql.org
Subject: Re: AWS forcing PG upgrade from v9.6 a disaster
Message-ID: <20210528213052.GC5649@momjian.us>
References: <88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com>
 <163214e4-0588-230b-9ed5-f682087e0e18@wi3ck.info>
 <4e238cc5-f63e-0435-63bf-2515500d5424@dunslane.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4e238cc5-f63e-0435-63bf-2515500d5424@dunslane.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210528213052.GC5649%40momjian.us>
Precedence: bulk

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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

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