From d7f316d28e58a38fc298ee5ee62030d4ae77a0ed Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 6 Dec 2006 15:40:11 +0000
Subject: [PATCH] Clean up psql -c documentation that uses \\.

---
 doc/src/sgml/ref/psql-ref.sgml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index 30d2710fd2..7e83b185bc 100644
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.176 2006/12/05 17:40:55 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.177 2006/12/06 15:40:11 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -87,9 +87,10 @@ PostgreSQL documentation
       it contains no <application>psql</application> specific features),
       or a single backslash command. Thus you cannot mix
       <acronym>SQL</acronym> and <application>psql</application>
-      meta-commands. To achieve that, you could pipe the string into
-      <application>psql</application>, like this: <literal>echo -e
-      "\\x\nSELECT * FROM foo;" | psql</literal>.
+      meta-commands with this option. To achieve that, you could
+      pipe the string into <application>psql</application>, like
+      this: <literal>echo "\x \\ SELECT * FROM foo;" | psql</literal>.
+      (<literal>\\</> is the separator meta-command.)
       </para>
       <para>
        If the command string contains multiple SQL commands, they are
-- 
2.40.0