Update "encode" documentation to mention that 'escape' only changes null

bytes and backslashes, remove "ASCII" mention.  Backpatch to 8.2.X.

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index ab179588c7e2a169aa9a4e5157b384c4ed97a6b7..b8be507f2df34457bbbc9fbd527b93432871f205 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.368 2007/02/20 18:18:05 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.369 2007/02/20 19:59:04 momjian Exp $ -->
 
  <chapter id="functions">
   <title>Functions and Operators</title>
@@ -1356,8 +1356,10 @@
        </entry>
        <entry><type>text</type></entry>
        <entry>
-        Encode binary data to <acronym>ASCII</acronym>-only representation.  Supported
+        Encode binary data to different representation.  Supported
         types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
+        <literal>Escape</> merely outputs null bytes as <literal>\000</> and
+        doubles backslashes.
        </entry>
        <entry><literal>encode( E'123\\000\\001', 'base64')</literal></entry>
        <entry><literal>MTIzAAE=</literal></entry>