summaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/alter_sequence.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/ref/alter_sequence.sgml')
-rw-r--r--doc/src/sgml/ref/alter_sequence.sgml8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/alter_sequence.sgml b/doc/src/sgml/ref/alter_sequence.sgml
index c6c3a7e33c0..28a81022aab 100644
--- a/doc/src/sgml/ref/alter_sequence.sgml
+++ b/doc/src/sgml/ref/alter_sequence.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.1 2003/03/20 07:02:07 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.2 2003/06/12 07:49:43 momjian Exp $
PostgreSQL documentation
-->
@@ -236,6 +236,12 @@ ALTER SEQUENCE serial RESTART WITH 105;
later aborts. This means that aborted transactions may leave unused "holes" in
the sequence of assigned values. setval operations are never rolled back, either.
</para>
+ <para>
+ <command>ALTER SEQUENCE</command> will not immediately affect backends, other than the
+ current one, which have cached sequence values. They must use up all cached values
+ prior to noticing the changed sequence parameters. The current backend will be
+ immediatly affected.
+ </para>
</refsect1>