From 202e6e73e6947b9c8baf9c8758618c1d8a5dcd73 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 2 Jun 2005 01:21:22 +0000
Subject: Add support for \x hex escapes in COPY.

Sergey Ten
---
 doc/src/sgml/ref/copy.sgml | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 0dd10d6754d..188f892fa0f 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.65 2005/05/07 02:22:45 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.66 2005/06/02 01:21:21 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -424,13 +424,18 @@ COPY <replaceable class="parameter">tablename</replaceable> [ ( <replaceable cla
        <entry>Backslash followed by one to three octal digits specifies
        the character with that numeric code</entry>
       </row>
+      <row>
+       <entry><literal>\x</><replaceable>digits</></entry>
+       <entry>Backslash <literal>x</> followed by one or two hex digits specifies
+       the character with that numeric code</entry>
+      </row>
      </tbody>
     </tgroup>
    </informaltable>
 
-    Presently, <command>COPY TO</command> will never emit an octal-digits
-    backslash sequence, but it does use the other sequences listed above
-    for those control characters.
+    Presently, <command>COPY TO</command> will never emit an octal or 
+    hex-digits backslash sequence, but it does use the other sequences
+    listed above for those control characters.
    </para>
 
    <para>
-- 
cgit v1.2.3