From 5569ae52ae206b3e35411df435884cf848ae0494 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Sun, 13 Feb 2011 09:29:01 -0500
Subject: Clarify documentation for libpq's PQescapeBytea to mention the new
 hex format.

Modify PQescapeStringConn() docs to be consisent with other escaping
functions.

Add mention problems with pre-9.0 versions of libpq using not understanding
bytea hex format to the 9.0 release notes.

Backpatch to 9.0 docs.
---
 doc/src/sgml/release-9.0.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'doc/src/sgml/release-9.0.sgml')

diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index 4902c058a96..f33ceea2264 100644
--- a/doc/src/sgml/release-9.0.sgml
+++ b/doc/src/sgml/release-9.0.sgml
@@ -2342,7 +2342,8 @@
       whether hex or traditional format is used for <type>bytea</>
       output.  Libpq's <function>PQescapeByteaConn()</> function automatically
       uses the hex format when connected to <productname>PostgreSQL</> 9.0
-      or newer servers.
+      or newer servers.  However, pre-9.0 libpq versions will not
+      correctly process hex format from newer servers.
      </para>
 
      <para>
-- 
cgit v1.2.3