mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Sigh, I managed to break the no-links-in-plain-text-docs rule too...

Browse Source
This commit is contained in:
Tom Lane 2009-12-19 05:37:01 +00:00
parent ce1489fa94
commit 0e9c1b1c99
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/src/sgml/release-8.5.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.12 2009/12/19 02:38:54 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.13 2009/12/19 05:37:01 tgl Exp $ -->
<sect1 id="release-8-5"> <sect1 id="release-8-5">
<title>Release 8.5alpha3</title> <title>Release 8.5alpha3</title>
@ -686,8 +686,8 @@
meant, sometimes resulting in surprising behavior. Now, PL/pgSQL meant, sometimes resulting in surprising behavior. Now, PL/pgSQL
can assume the variable is meant, or assume the table column is can assume the variable is meant, or assume the table column is
meant, or throw an error in ambiguous cases. For safety the default meant, or throw an error in ambiguous cases. For safety the default
is to throw error. To configure this see <xref is to throw error. To configure this see <link
linkend="plpgsql-var-subst">.</emphasis> linkend="plpgsql-var-subst">the PL/pgSQL documentation</link>.</emphasis>
</para> </para>
<para> <para>
<emphasis>Error reporting is much nicer: it no longer shows edited <emphasis>Error reporting is much nicer: it no longer shows edited
@ -697,12 +697,12 @@
<para> <para>
<emphasis>Note that this change affects the set of keywords that are <emphasis>Note that this change affects the set of keywords that are
reserved in PL/pgSQL (i.e., cannot be the name of a PL/pgSQL reserved in PL/pgSQL (i.e., cannot be the name of a PL/pgSQL
variable). Now, all keywords shown as reserved in <xref variable). Now, all keywords shown as reserved in <link
linkend="sql-keywords-appendix"> are reserved for PL/pgSQL purposes linkend="sql-keywords-appendix">Appendix C</link> are reserved for
as well. However, many PL/pgSQL-only keywords that were formerly PL/pgSQL purposes as well. However, many PL/pgSQL-only keywords
treated as reserved no longer are. As in regular SQL, you can that were formerly treated as reserved no longer are. As in regular
double-quote a variable's name if you want to use a name that SQL, you can double-quote a variable's name if you want to use a
conflicts with a reserved keyword.</emphasis> name that conflicts with a reserved keyword.</emphasis>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>