@@ -527,14 +527,10 @@ int lo_unlink(PGconn *conn, Oid lobjId);
527527
528528 <para>
529529 There are server-side functions callable from SQL that correspond to
530- each of the client-side functions described above(please note
531- that the server side function
532- for <function>lo_read</function> is <function>loread</function> and
533- the server side function for <function>lo_write</function>
534- is <function>lowrite</function>); indeed, for the most part the
535- client-side functions are simply interfaces to the equivalent
536- server-side functions. The ones that are actually useful to call
537- via SQL commands are
530+ each of the client-side functions described above; indeed, for the
531+ most part the client-side functions are simply interfaces to the
532+ equivalent server-side functions. The ones that are actually useful
533+ to call via SQL commands are
538534 <function>lo_creat</function><indexterm><primary>lo_creat</></>,
539535 <function>lo_create</function><indexterm><primary>lo_create</></>,
540536 <function>lo_unlink</function><indexterm><primary>lo_unlink</></>,
@@ -576,6 +572,14 @@ SELECT lo_export(image.raster, '/tmp/motd') FROM image
576572 The client-side functions do not require superuser privilege.
577573 </para>
578574
575+ <para>
576+ The functionality of <function>lo_read</function> and
577+ <function>lo_write</function> is also available via server-side calls,
578+ but the names of the server-side functions differ from the client side
579+ interfaces in that they do not contain underscores. You must call
580+ these functions as <function>loread</> and <function>lowrite</>.
581+ </para>
582+
579583</sect1>
580584
581585<sect1 id="lo-examplesect">