psql lo_export documentation

From: Jorgen Austvik - Sun Norway <Jorgen(dot)Austvik(at)Sun(dot)COM>
To: pgsql-general(at)postgresql(dot)org
Subject: psql lo_export documentation
Date: 2007-11-30 10:31:01
Message-ID: 474FE665.5000803@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

The 8.3 psql documentation says this about lo_export:

------8<------------8<------------8<------------8<------------8<------------8<------
<varlistentry>
<term><literal>\lo_export <replaceable
class="parameter">loid</replaceable> <replaceable
class="parameter">filename</replaceable></literal></term>

<listitem>
<para>
Reads the large object with <acronym>OID</acronym> <replaceable
class="parameter">loid</replaceable> from the database and
writes it to <replaceable
class="parameter">filename</replaceable>. Note that this is
subtly different from the server function
<function>lo_export</function>, which acts with the permissions
of the user that the database server runs as and on the server's
file system.
</para>
<tip>
<para>
Use <command>\lo_list</command> to find out the large object's
<acronym>OID</acronym>.
</para>
</tip>
</listitem>
</varlistentry>
------8<------------8<------------8<------------8<------------8<------------8<------

Below is an error message I get when I try to use lo_export from client:

------8<------------8<------------8<------------8<------------8<------------8<------
other_database=> SELECT lo_export(16391, '/tmp/file') FROM
lotest_stash_values;
ERROR: must be superuser to use server-side lo_export()
HINT: Anyone can use the client-side lo_export() provided by libpq.
------8<------------8<------------8<------------8<------------8<------------8<------

With experiments I find that lo_export on 8.3 stores the files on the
database server file system. I also think it would be good if the
documentation said that you need to be database superuser to use this

Something along the lines of this?

Note that this acts with the permissions of the user that the
database server runs as and on the server's file system. Therefore you
have to be a database superuser to be allowed to use this function.

On 8.2 I get this on client side import, this is fixed in 8.3.
------8<------------8<------------8<------------8<------------8<------------8<------
other_database=> INSERT INTO lotest_stash_values (loid) SELECT
lo_import('/export/home/ja155679/random_data.dat');
ERROR: must be superuser to use server-side lo_import()
HINT: Anyone can use the client-side lo_import() provided by libpq.
------8<------------8<------------8<------------8<------------8<------------8<------

So, on 8.2 it looks for me like you had to be database superuser to be
able to run lo_import, and that files would import from the server, and
that that now is changed in 8.3 so that the files are imported from the
client.

Do we really want lo_import and lo_export to work on different file systems?

-J
--

Jørgen Austvik, Software Engineering - QA
Sun Microsystems Database Technology Group

Attachment Content-Type Size
jorgen.austvik.vcf text/x-vcard 391 bytes

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2007-11-30 10:31:13 Re: log_line_prefix='%t %u %d %h %p %i %l %x ' causes error
Previous Message Madison Kelly 2007-11-30 10:22:34 Moving lock file (/tmp/.s.PGSQL.<port>)