Improve description of loread/lowrite.

Patch by me, reviewed by Tatsuo Ishii.

diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index 6dbc84c03ec45389c36cb3786391486293117d60..dcd5e82580dfff16fe6218cd977c1ff7d91aef27 100644 (file)
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -527,14 +527,10 @@ int lo_unlink(PGconn *conn, Oid lobjId);
 
   
    There are server-side functions callable from SQL that correspond to
-   each of the client-side functions described above(please note
-   that the server side function
-   for lo_read is loread and
-   the server side function for lo_write
-   is lowrite); 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; 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
    lo_creatlo_creat,
    lo_createlo_create,
    lo_unlinklo_unlink,
@@ -576,6 +572,14 @@ SELECT lo_export(image.raster, '/tmp/motd') FROM image
     The client-side functions do not require superuser privilege.
   
 
+  
+    The functionality of lo_read and
+    lo_write is also available via server-side calls,
+    but the names of the server-side functions differ from the client side
+    interfaces in that they do not contain underscores.  You must call
+    these functions as loread and lowrite.
+  
+