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

diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml
index eedb91d954dbd413904cfea1182681f72457143f..cf743aa2f769602c8d1a6104c52b348faff6818c 100644 (file)
--- a/doc/src/sgml/release-10.sgml
+++ b/doc/src/sgml/release-10.sgml
@@ -151,6 +151,43 @@
 
     
 
+     
+      Move sequences' metadata fields into a new 
+      linkend="catalog-pg-sequence">pg_sequence
+      system catalog (Peter Eisentraut)
+     
+
+     
+      A sequence relation now stores only the fields that can be modified
+      by nextval(), that
+      is last_value, log_cnt,
+      and is_called.  Other sequence properties, such as
+      the starting value and increment, are kept in a corresponding row of
+      the pg_sequence catalog.
+      ALTER SEQUENCE updates are now fully transactional,
+      implying that the sequence is locked until commit.
+      The nextval() and setval() functions
+      remain nontransactional.
+     
+
+     
+      The main incompatibility introduced by this change is that selecting
+      from a sequence relation now returns only the three fields named
+      above.  To obtain the sequence's other properties, applications must
+      look into pg_sequence.  The new system
+      view pg_sequences
+      can also be used for this purpose; it provides column names that are
+      more compatible with existing code.
+     
+    
+
+    
+
      
@@ -875,35 +912,6 @@
 
       
 
-       
-        Create a 
-        linkend="catalog-pg-sequence">pg_sequence
-        system catalog to store sequence metadata (Peter Eisentraut)
-       
-
-       
-        Sequence metadata includes the start, increment, etc, properties.
-        ALTER SEQUENCE updates are now fully transactional,
-        implying that the sequence is locked until commit.  Sequences'
-        current values are still stored in individual table files, and
-        the nextval() and setval() functions
-        remain nontransactional.
-       
-
-       
-        Also
-        add pg_sequences
-        view to show all sequences.
-       
-      
-
-      
-