Re: [HACKERS] pg_upgrade vs extension upgrades
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] pg_upgrade vs extension upgrades |
Дата | |
Msg-id | ba6343db-94d9-6103-fb7d-081ec05760e6@2ndquadrant.com обсуждение исходный текст |
Ответ на | [HACKERS] pg_upgrade vs extension upgrades (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: [HACKERS] pg_upgrade vs extension upgrades
Re: [HACKERS] pg_upgrade vs extension upgrades |
Список | pgsql-hackers |
On 4/10/17 11:30, Magnus Hagander wrote: > 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? Shouldn't pg_dump do this, and perhaps by default? If I restore a dump into another instance, I need to upgrade all my extensions to that installations's versions, no? That's not particular to pg_upgrade. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: