| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Planning incompatibilities for Postgres 10.0 |
| Date: | 2013-05-27 15:38:23 |
| Message-ID: | 20130527153823.GT15045@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Yes, we should be collecting things we want to do for a pg_upgrade break
> > so we can see the list all in one place.
>
> Precisely. We've said right along that we reserve the right to have a
> non-upgradable disk format change whenever sufficiently many reasons
> accumulate to do that.
Do we have a wiki page about this?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-05-27 16:05:50 | Re: Planning incompatibilities for Postgres 10.0 |
| Previous Message | Alvaro Herrera | 2013-05-27 15:36:50 | Re: Planning incompatibilities for Postgres 10.0 |