Re: Inefficient handling of LO-restore + Patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mario Weilguni <mario(dot)weilguni(at)icomedias(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inefficient handling of LO-restore + Patch
Date: 2002-04-15 19:17:10
Message-ID: 200204151917.g3FJHA610870@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-04-15 19:17:27 Re: Array Iterator functions
Previous Message Neil Conway 2002-04-15 19:07:19 regression in CVS HEAD