| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade vs extension upgrades |
| Date: | 2017-04-10 16:53:38 |
| Message-ID: | CA+TgmoZR_uqenNrZq9zYpGj1JNAogzZyJUXdkqDt01PT-Up7nQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 10, 2017 at 11:30 AM, Magnus Hagander <magnus(at)hagander(dot)net> 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?
I don't know whether it's useful, but I doubt it would hurt anything.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-04-10 16:55:12 | Re: GSOC'17 project introduction: Parallel COPY execution with errors handling |
| Previous Message | Peter Eisentraut | 2017-04-10 16:52:21 | Re: logical replication worker and statistics |