From 0e9c1b1c996863b030328d2c1b404bdb65f4ac56 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 19 Dec 2009 05:37:01 +0000 Subject: [PATCH] Sigh, I managed to break the no-links-in-plain-text-docs rule too... --- doc/src/sgml/release-8.5.sgml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/src/sgml/release-8.5.sgml b/doc/src/sgml/release-8.5.sgml index 668c2adc2f..12f9eff68c 100644 --- a/doc/src/sgml/release-8.5.sgml +++ b/doc/src/sgml/release-8.5.sgml @@ -1,4 +1,4 @@ - + Release 8.5alpha3 @@ -686,8 +686,8 @@ meant, sometimes resulting in surprising behavior. Now, PL/pgSQL can assume the variable is meant, or assume the table column is meant, or throw an error in ambiguous cases. For safety the default - is to throw error. To configure this see . + is to throw error. To configure this see the PL/pgSQL documentation. Error reporting is much nicer: it no longer shows edited @@ -697,12 +697,12 @@ 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 - variable). Now, all keywords shown as reserved in are reserved for PL/pgSQL purposes - as well. However, many PL/pgSQL-only keywords that were formerly - treated as reserved no longer are. As in regular SQL, you can - double-quote a variable's name if you want to use a name that - conflicts with a reserved keyword. + variable). Now, all keywords shown as reserved in Appendix C are reserved for + PL/pgSQL purposes as well. However, many PL/pgSQL-only keywords + that were formerly treated as reserved no longer are. As in regular + SQL, you can double-quote a variable's name if you want to use a + name that conflicts with a reserved keyword.