| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade vs extension upgrades |
| Date: | 2017-04-12 22:30:58 |
| Message-ID: | ba6343db-94d9-6103-fb7d-081ec05760e6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-12 22:31:33 | Re: SUBSCRIPTIONS and pg_upgrade |
| Previous Message | Álvaro Hernández Tortosa | 2017-04-12 21:37:37 | Re: Letting the client choose the protocol to use during a SASL exchange |