summaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/alter_sequence.sgml
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2003-06-12 07:49:43 +0000
committerBruce Momjian <bruce@momjian.us>2003-06-12 07:49:43 +0000
commite9cda08b2b79303e36594e1d4e5e09ea2db84b6a (patch)
treeaced1feff6e484d853727aab3673c85d8de3cbcc /doc/src/sgml/ref/alter_sequence.sgml
parentb4cea00a1fc9d2270bfe9aeeee44915378d5f733 (diff)
Brief note about sequence cache not being cleared in other backends.
Actually clear the cache in the backend making the alteration. This follows in the footsteps of setval(). Rod Taylor
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>