| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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 23:37:15 |
| Message-ID: | 8ed2c7ee-3a85-0ec0-4913-06ebf850f760@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/12/17 18:59, Robert Haas wrote:
> I do think there might be some value in a tool that looked for old
> extensions and tried to update them, but I'm not sure it should be
> pg_dump.
This reminds me a bit of the problem of upgrading all collations after
an upgrade. Perhaps we can find similar solutions to both problems.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2017-04-12 23:37:17 | Re: pg_statistic_ext.staenabled might not be the best column name |
| Previous Message | Peter Eisentraut | 2017-04-12 23:22:59 | Re: Foreign Join pushdowns not working properly for outer joins |