doc: Update ALTER SEQUENCE claims about changes being nontransactional

petere · petere · commit a35ac7c4e3cc · 2017-05-02T10:34:49.000-04:00
Clarify that all changes except RESTART are transactional (since 1753b1b). Reported-by: Michael Paquier <michael.paquier@gmail.com>
diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml
@@ -180,6 +180,14 @@ ALTER SEQUENCE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> S
         the start value that was recorded by <command>CREATE SEQUENCE</>
         or last set by <command>ALTER SEQUENCE START WITH</>.
        </para>
+
+       <para>
+        Like a <function>setval</function> call, a <literal>RESTART</literal>
+        operation on a sequence is never rolled back, to avoid blocking of
+        concurrent transactions that obtain numbers from the same sequence.
+        (The other clauses cause ordinary catalog updates that can be rolled
+        back.)
+       </para>
       </listitem>
      </varlistentry>
 
@@ -281,15 +289,6 @@ ALTER SEQUENCE [ IF EXISTS ] <replaceable class="parameter">name</replaceable> S
  <refsect1>
   <title>Notes</title>
 
-  <para>
-   To avoid blocking of concurrent transactions that obtain numbers from the
-   same sequence, <command>ALTER SEQUENCE</command>'s effects on the sequence
-   generation parameters are never rolled back; those changes take effect
-   immediately and are not reversible.  However, the <literal>OWNED BY</>,
-   <literal>OWNER TO</>, <literal>RENAME TO</>, and <literal>SET SCHEMA</>
-   clauses cause ordinary catalog updates that can be rolled back.
-  </para>
-
   <para>
    <command>ALTER SEQUENCE</command> will not immediately affect
    <function>nextval</> results in backends,
