From f95b5334a759c9e225a6c8e701899c5cd601541a Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 27 Jun 2008 02:44:31 +0000
Subject: [PATCH] Mention actual function names in documentation of how to pass
 binary values to libpq.

---
 doc/src/sgml/libpq.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 629e501b8a..deb052e5c4 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.259 2008/06/23 21:10:49 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.260 2008/06/27 02:44:31 momjian Exp $ -->
 
 <chapter id="libpq">
  <title><application>libpq</application> - C Library</title>
@@ -1403,7 +1403,9 @@ PGresult *PQexecParams(PGconn *conn,
             For example, integers must be passed in network byte
             order.  Passing <type>numeric</> values requires
             knowledge of the server storage format, as implemented
-            in <filename>src/backend/utils/adt/numeric.c</>.
+            in
+            <filename>src/backend/utils/adt/numeric.c::numeric_send()</> and
+            <filename>src/backend/utils/adt/numeric.c::numeric_recv()</>.
            </para>
           </listitem>
          </varlistentry>
-- 
2.40.0