Re: Postgres, Perl, and Large Objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: S Vahey <savahey(at)yahoo(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Postgres, Perl, and Large Objects
Date: 2001-01-19 16:10:54
Message-ID: 8674.979920654@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

S Vahey <savahey(at)yahoo(dot)com> writes:
> You must have Postgres superupser privilege to use server-side
> lo_import(). Anyone can use the client-side lo_import provided by
> libpq.

That means exactly what it says: you can't use the lo_import (or
lo_export) SQL functions unless you are superuser. This is a security
issue, not a transaction issue: those functions let you read or scribble
on any file that's accessible to the Postgres userid.

I don't know whether the DBI interface provides access to client-side
large-object functions; you might have to use the Pg "perl5" interface
library instead. Or run your application connected as the database
superuser, but that seems like a risky way to fly.

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Andy Holman 2001-01-19 21:13:21 Re: Postgres access using PHP3
Previous Message John Poltorak 2001-01-19 15:26:36 Postgres access using PHP3