From: Peter Eisentraut Date: Tue, 2 May 2017 14:34:49 +0000 (-0400) Subject: doc: Update ALTER SEQUENCE claims about changes being nontransactional X-Git-Tag: REL_10_BETA1~121 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a35ac7c4e3ccf93876b4652d94a418fc82e0eda3;p=postgresql doc: Update ALTER SEQUENCE claims about changes being nontransactional Clarify that all changes except RESTART are transactional (since 1753b1b027035029c2a2a1649065762fafbf63f3). Reported-by: Michael Paquier --- diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml index 5c912ab892..3fb3400d6b 100644 --- a/doc/src/sgml/ref/alter_sequence.sgml +++ b/doc/src/sgml/ref/alter_sequence.sgml @@ -180,6 +180,14 @@ ALTER SEQUENCE [ IF EXISTS ] name S the start value that was recorded by CREATE SEQUENCE or last set by ALTER SEQUENCE START WITH. + + + Like a setval call, a RESTART + 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.) + @@ -281,15 +289,6 @@ ALTER SEQUENCE [ IF EXISTS ] name S Notes - - To avoid blocking of concurrent transactions that obtain numbers from the - same sequence, ALTER SEQUENCE's effects on the sequence - generation parameters are never rolled back; those changes take effect - immediately and are not reversible. However, the OWNED BY, - OWNER TO, RENAME TO, and SET SCHEMA - clauses cause ordinary catalog updates that can be rolled back. - - ALTER SEQUENCE will not immediately affect nextval results in backends,