I doubt you actually need to run pg_upgrade to test this. Just start up a different server version on the same host/port.
On Thu, Jun 4, 2020 at 10:45 AM Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi Hackers, > > Please find the attached patch which fixes the server old version cache > issue on pg upgrade. > > Steps to Reproduce Issue - > 1.Install & Start pg11. > 2.Create table in database from pgAdmin. > 3.Upgrade pg11 to pg12 using pg_upgrade.(Refer link > <https://info.crunchydata.com/blog/how-to-perform-a-major-version-upgrade-using-pg_upgrade-in-postgresql> > ) > 4.Try accessing the same server & table. Due to the cached version above > error will be shown if you run select command for existing table. > 5.Patch will refresh database version after re-connection on pg-upgrade. > > Thanks, > Yogesh Mahajan > QA - Team > EnterpriseDB Corporation > > Phone: +91-9741705709 > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
