@@ -396,14 +396,10 @@ int lo_unlink(PGconn *conn, Oid lobjId);
396
396
397
397
<para>
398
398
There are server-side functions callable from SQL that correspond to
399
- each of the client-side functions described above(please note
400
- that the server side function
401
- for <function>lo_read</function> is <function>loread</function> and
402
- the server side function for <function>lo_write</function>
403
- is <function>lowrite</function>); indeed, for the most part the
404
- client-side functions are simply interfaces to the equivalent
405
- server-side functions. The ones that are actually useful to call
406
- via SQL commands are
399
+ each of the client-side functions described above; indeed, for the
400
+ most part the client-side functions are simply interfaces to the
401
+ equivalent server-side functions. The ones that are actually useful
402
+ to call via SQL commands are
407
403
<function>lo_creat</function><indexterm><primary>lo_creat</></>,
408
404
<function>lo_create</function><indexterm><primary>lo_create</></>,
409
405
<function>lo_unlink</function><indexterm><primary>lo_unlink</></>,
@@ -445,6 +441,15 @@ SELECT lo_export(image.raster, '/tmp/motd') FROM image
445
441
The client-side functions can be used by any
446
442
<productname>PostgreSQL</productname> user.
447
443
</para>
444
+
445
+ <para>
446
+ The functionality of <function>lo_read</function> and
447
+ <function>lo_write</function> is also available via server-side calls,
448
+ but the names of the server-side functions differ from the client side
449
+ interfaces in that they do not contain underscores. You must call
450
+ these functions as <function>loread</> and <function>lowrite</>.
451
+ </para>
452
+
448
453
</sect1>
449
454
450
455
<sect1 id="lo-examplesect">
0 commit comments