From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nelson Gonzaga <ngonzaga@yahoo.com>
cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: Grant on lo_export()
In-reply-to: <1160328940.343057.1533121961953@mail.yahoo.com>
References: <1160328940.343057.1533121961953.ref@mail.yahoo.com>
 <1160328940.343057.1533121961953@mail.yahoo.com>
Comments: In-reply-to Nelson Gonzaga <ngonzaga@yahoo.com>
	message dated "Wed, 01 Aug 2018 11:12:41 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <27169.1533132366.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 01 Aug 2018 10:06:06 -0400
Message-ID: <27170.1533132366@sss.pgh.pa.us>
Precedence: bulk

Nelson Gonzaga <ngonzaga@yahoo.com> writes:
> Hi all,I'm trying to use lo_import / lo_export and apparently I have per=
mission denied:
> command:select lo_export(oid_imagem, '/tmp2/erro_export1.png') fromimage=
m where nome_imagem =3D 'erro';
> ERROR: must be superuser to use server-side lo_export()
> SQL state:42501
> Hint:Anyone can use the client-side lo_export() provided by libpq.

The error message means exactly what it says.

As of v11 it'll be possible to grant usage of lo_export() to
non-superusers, but in all released branches that check is hard-wired.

Note that since you can use that function to overwrite PG data or config
files, granting use of it to someone you wouldn't trust with full
superuser would be a damfool idea anyway.

			regards, tom lane