summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuo Ishii2013-06-11 05:25:58 +0000
committerTatsuo Ishii2013-06-11 05:29:25 +0000
commit219ef8e33ce09725a9ae1c345c63b98884a101d6 (patch)
tree9a6db8f8086c72716956cd0f273d3449f200e5b9
parent86742ac9c838cb383f951703f28938d371cb7858 (diff)
Add description that loread()/lowrite() are corresponding to
lo_read()/lo_write() in libpq to avoid confusion.
-rw-r--r--doc/src/sgml/lobj.sgml12
1 files 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</></>,