Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
| От | Craig Ringer |
|---|---|
| Тема | Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0 |
| Дата | |
| Msg-id | CAMsr+YHB91+cnwbimwD4b9XQUztm5cVnHMY89FRpbfVzXUrZpA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0 (Justin Clift <justin@postgresql.org>) |
| Список | pgsql-hackers |
On 12 April 2016 at 00:39, Justin Clift <justin@postgresql.org> wrote:
Moving over a conversation from the pgsql-advocacy mailing list. In it
Simon (CC'd) raised the issue of potentially creating a backwards-compatibility
breaking release at some point in the future, to deal with things that
might have no other solution (my wording).
Relevant part of that thread there for reference:
http://www.postgresql.org/message-id/CANP8+jLtk1NtaJyXc=hAqX=0k+ku4zfavgVBKfs+_sOr9hepNQ@mail.gmail.com
Simon included a short starter list of potentials which might be in
that category:
* SQL compliant identifiers
* Remove RULEs
* Change recovery.conf
* Change block headers
* Retire template0, template1
* Optimise FSM
* Add heap metapage
* Alter tuple headers
et al
+
* v4 protocol (feature negotiation, lazy blob fetching, etc)
* retire pg_hba.conf and use SQL access management
?
В списке pgsql-hackers по дате отправления: