Server side lo-funcs name

Recently we got a complain about server side large object function
names described in the doc:
http://www.postgresql.org/message-id/51B2413F.8010305@gmail.com

In the doc:
http://www.postgresql.org/docs/9.3/static/lo-funcs.html

"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"

From the description it is hard for users to find out server side
functions "loread" and "lowrite" becuase they are looking for
"lo_read" and "lo_write". So I think his complain is fair. Included
patches attempt to fix the problem.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index db5bc10..6dbc84c 100644
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -527,10 +527,14 @@ int lo_unlink(PGconn *conn, Oid lobjId);  <para>   There are server-side functions callable from
SQLthat 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</></>,