| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: 9.6 -> 10.0 |
| Date: | 2016-04-06 21:56:46 |
| Message-ID: | CA+TgmoaSHW6HcOMCD9jEyJ4tjVauaZJPRmfPOiYbD3GptQurxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Wed, Apr 6, 2016 at 4:56 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> So the first question needs to be not "When?" but "Should we?" Before that
> can be answered we need a list of TODO items that would break pg_upgrade as
> it exists today. Then some thought can be put into what it would take to
> support an in-place upgrade with those changes. MAYBE it turns out that it's
> just too much effort and we do need a break, but that needs to be a very
> well justified decision.
Well said.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-04-06 22:04:41 | Re: 9.6 -> 10.0 |
| Previous Message | Jim Nasby | 2016-04-06 20:56:55 | Re: 9.6 -> 10.0 |