aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/release.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/release.sgml')
-rw-r--r--doc/src/sgml/release.sgml21
1 files changed, 20 insertions, 1 deletions
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 092179f01bc..37d67a94797 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.380 2005/09/28 21:22:12 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.381 2005/10/02 23:50:06 tgl Exp $
Typical markup:
@@ -393,6 +393,25 @@ pg_[A-Za-z0-9_] <application>
<listitem>
<para>
+ Sequence arguments of <function>nextval()</> and related functions
+ are now bound early by default (Tom)
+ </para>
+ <para>
+ When an expression like <literal>nextval('myseq')</> appears in a
+ column default expression or view, the referenced sequence (here
+ <literal>myseq</>) is now looked up immediately, and its pg_class
+ OID is placed in the stored expression. This representation will
+ survive renaming of the referenced sequence, as well as changes in
+ schema search paths. The system also understands that the sequence
+ reference represents a dependency, so the sequence cannot be dropped
+ without dropping the referencing object. To get the old behavior of
+ run-time lookup of the sequence by name, cast the argument to
+ <type>text</>, for example <literal>nextval('myseq'::text)</>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
In <application>psql</application>, treat unquoted
<literal>\{digit}+</> sequences as octal (Bruce)
</para>