| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: obsolete code in pg_upgrade |
| Date: | 2017-08-24 19:32:04 |
| Message-ID: | 8aa00f15-144e-e793-750e-d1d6876d6a7e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/23/17 09:36, Robert Haas wrote:
> I think I agree. It seems to me that the version of pg_upgrade
> shipped with release N only needs to support upgrades to release N,
> not older releases. There's probably room for debate about whether a
> pg_upgrade needs to support direct upgrades FROM very old releases,
> but we need not decide anything about that right now.
>
> I think you could go ahead and rip out this code, but as it seems like
> a non-critical change, -1 for back-patching it.
committed to PG10 and master
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-24 19:44:37 | Re: Proposal: global index |
| Previous Message | Andres Freund | 2017-08-24 19:07:28 | Re: Standby corruption after master is restarted |