[HACKERS] pg_upgrade vs extension upgrades - Mailing list pgsql-hackers

From Magnus Hagander
Subject [HACKERS] pg_upgrade vs extension upgrades
Date
Msg-id CABUevEyb38S0ApKpNNh1q_6zFnAwmqVjRauVg1uvJL9qRpxjHA@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] pg_upgrade vs extension upgrades  (Robert Haas <robertmhaas@gmail.com>)
Re: [HACKERS] pg_upgrade vs extension upgrades  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] pg_upgrade vs extension upgrades  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
After you've run pg_upgrade, you have to loop through all your databases and do an "ALTER EXTENSION abc UPDATE" once for each extension.

Is there a reason we shouldn't have pg_upgrade emit a script that does this, similar to how it emits a script to run ANALYZE?

--

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] pg_dump emits ALTER TABLE ONLY partitioned_table
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] RMT: Use Visual Studio 2015 for Compiling and linkingthe Windows version in PG10