database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-25 12:03:53 +03:00
Code Activity

Brief note about sequence cache not being cleared in other backends.

Browse Source 
Actually clear the cache in the backend making the alteration.  This
follows in the footsteps of setval().

Rod Taylor
This commit is contained in:
Bruce Momjian
2003-06-12 07:49:43 +00:00
parent b4cea00a1f
commit e9cda08b2b
4 changed files with 55 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/ref/alter_sequence.sgml
View File

@@ -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>