From 09ab9b591510a8f5fe1dcfc9b8f1cd6ff73f063e Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 30 Nov 2003 05:45:22 +0000
Subject: [PATCH] Remove INTO recommendation for plpgsql language.

---
 doc/src/sgml/plpgsql.sgml | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index c3502df3f5..85fb11a88e 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.31 2003/11/30 04:47:37 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.32 2003/11/30 05:45:22 momjian Exp $
 -->
 
 <chapter id="plpgsql"> 
@@ -957,11 +957,8 @@ SELECT INTO <replaceable>target</replaceable> <replaceable>select_expressions</r
     </para>
 
     <para>
-     At present, the <literal>INTO</> clause can appear almost anywhere in the <command>SELECT</command>
-     statement, but it is recommended to place it immediately after the <literal>SELECT</literal>
-     key word as depicted above.  Future versions of
-     <application>PL/pgSQL</application> may be less forgiving about
-     placement of the <literal>INTO</literal> clause.
+     The <literal>INTO</> clause can appear almost anywhere in the <command>SELECT</command>
+     statement.
     </para>
 
     <para>