| From: | Justin Clift <justin(at)postgresql(dot)org> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(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-09 19:07:52 |
| Message-ID: | 4F103D30-5861-4A63-BD2A-2925E0A6A6CA@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 9 Apr 2016, at 19:50, Jim Nasby <jim(at)nasby(dot)net> wrote:
> On 4/7/16 1:54 AM, Simon Riggs wrote:
<snip>
>> By hand-wavy, you mean not fully worked out? Yes, neither the pros and
>> cons have been worked out in detail, so opposing the idea is on the same
>> shaky ground. How then to proceed?
>
> Do we even have a list of things we'd like to do that would break compatibility? I haven't seen one...
Simon's email a few weeks ago is probably a decent starting point:
From that:
* SQL compliant identifiers
* Remove RULEs
* Change recovery.conf
* Change block headers
* Retire template0, template1
* Optimise FSM
* Add heap metapage
* Alter tuple headers
et al
+ Justin
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-04-10 23:23:04 | Re: 9.6 -> 10.0 |
| Previous Message | Jim Nasby | 2016-04-09 18:50:02 | Re: 9.6 -> 10.0 |