Re: Inefficient handling of LO-restore + Patch - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Inefficient handling of LO-restore + Patch
Date
Msg-id 200204151917.g3FJHA610870@candle.pha.pa.us
Whole thread Raw
In response to Re: Inefficient handling of LO-restore + Patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Inefficient handling of LO-restore + Patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Mario Weilguni" <mario.weilguni@icomedias.com> writes:
> > * select octet_length(data) from pg_largeobject where loid=OIDOFOBJECT and pageno=0
> 
> This really should not work if you're not superuser.  Right now it does,
> but I think that's an oversight in the default permissions settings for
> system tables.  Anyone object if I turn off public read access to
> pg_largeobject?

Please do whatever you can to tighten it up. I thought we needed to keep
read access so people could get to their large objects, but maybe not.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: RFC: Generating useful names for foreign keys and checks
Next
From: Tom Lane
Date:
Subject: Re: Array Iterator functions