summaryrefslogtreecommitdiff
path: root/doc/src/sgml/release-9.0.sgml
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-02-13 09:29:01 -0500
committerBruce Momjian <bruce@momjian.us>2011-02-13 09:29:01 -0500
commit5569ae52ae206b3e35411df435884cf848ae0494 (patch)
tree76dd10372f46de94d6b08b2782422113c2740ee6 /doc/src/sgml/release-9.0.sgml
parentcebbaa1d5d2729c1b9dde0b472b4b034ef2f44b0 (diff)
downloadpostgresql-5569ae52ae206b3e35411df435884cf848ae0494.tar.gz
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.
Diffstat (limited to 'doc/src/sgml/release-9.0.sgml')
-rw-r--r--doc/src/sgml/release-9.0.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index 4902c058a9..f33ceea226 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>