@@ -411,14 +411,10 @@ int lo_unlink(PGconn *conn, Oid lobjId);
411411
412412 <para>
413413 There are server-side functions callable from SQL that correspond to
414- each of the client-side functions described above(please note
415- that the server side function
416- for <function>lo_read</function> is <function>loread</function> and
417- the server side function for <function>lo_write</function>
418- is <function>lowrite</function>); indeed, for the most part the
419- client-side functions are simply interfaces to the equivalent
420- server-side functions. The ones that are actually useful to call
421- via SQL commands are
414+ each of the client-side functions described above; indeed, for the
415+ most part the client-side functions are simply interfaces to the
416+ equivalent server-side functions. The ones that are actually useful
417+ to call via SQL commands are
422418 <function>lo_creat</function><indexterm><primary>lo_creat</></>,
423419 <function>lo_create</function><indexterm><primary>lo_create</></>,
424420 <function>lo_unlink</function><indexterm><primary>lo_unlink</></>,
@@ -460,6 +456,14 @@ SELECT lo_export(image.raster, '/tmp/motd') FROM image
460456 The client-side functions do not require superuser privilege.
461457 </para>
462458
459+ <para>
460+ The functionality of <function>lo_read</function> and
461+ <function>lo_write</function> is also available via server-side calls,
462+ but the names of the server-side functions differ from the client side
463+ interfaces in that they do not contain underscores. You must call
464+ these functions as <function>loread</> and <function>lowrite</>.
465+ </para>
466+
463467</sect1>
464468
465469<sect1 id="lo-examplesect">