From c571b5168e55f2d98f5b3051ff56992edff506f5 Mon Sep 17 00:00:00 2001
From: Tatsuo Ishii <ishii@postgresql.org>
Date: Tue, 11 Jun 2013 14:25:58 +0900
Subject: [PATCH] Add description that loread()/lowrite() are corresponding to
lo_read()/lo_write() in libpq to avoid confusion.
---
doc/src/sgml/lobj.sgml | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index 291409fde0b..74bd91d13e4 100644
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -411,10 +411,14 @@ int lo_unlink(PGconn *conn, Oid lobjId);
<para>
There are server-side functions callable from SQL that correspond to
- each of the client-side functions described above; indeed, for the
- most part the client-side functions are simply interfaces to the
- equivalent server-side functions. The ones that are actually useful
- to call via SQL commands are
+ each of the client-side functions described above(please note
+ that the server side function
+ for <function>lo_read</function> is <function>loread</function> and
+ the server side function for <function>lo_write</function>
+ is <function>lowrite</function>); indeed, for the most part the
+ client-side functions are simply interfaces to the equivalent
+ server-side functions. The ones that are actually useful to call
+ via SQL commands are
<function>lo_creat</function><indexterm><primary>lo_creat</></>,
<function>lo_create</function><indexterm><primary>lo_create</></>,
<function>lo_unlink</function><indexterm><primary>lo_unlink</></>,
--
GitLab