pgsql: In v10 release notes, call out sequence changes as a compatibili

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: In v10 release notes, call out sequence changes as a compatibili
Date: 2017-07-20 19:28:48
Message-ID: E1dYH7w-0004va-9S@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

In v10 release notes, call out sequence changes as a compatibility item.

The previous description didn't make it clear that this change
potentially breaks applications, partly because the entry wasn't even
in the compatibility-hazard section. Move and clarify.

Discussion: https://postgr.es/m/603f3f0a-f89d-ae8b-1da9-a92fac16086d@enterprisedb.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/866f4a7c210857aa342bf901558d170325094dde

Modified Files
--------------
doc/src/sgml/release-10.sgml | 66 +++++++++++++++++++++++++-------------------
1 file changed, 37 insertions(+), 29 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2017-07-21 08:24:37 pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b
Previous Message Tom Lane 2017-07-20 16:42:07 pgsql: Doc: clarify description of degenerate NATURAL joins.