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

From Mario Weilguni
Subject Re: Inefficient handling of LO-restore + Patch
Date
Msg-id D143FBF049570C4BB99D962DC25FC2D2178104@freedom.icomedias.com
Whole thread Raw
In response to Inefficient handling of LO-restore + Patch  ("Mario Weilguni" <mario.weilguni@icomedias.com>)
List pgsql-hackers
And how about getting database internals via SQL-functions - e.g. getting BLCSIZE, LOBBLCSIZE?

-----Ursprüngliche Nachricht-----
Von: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Gesendet: Montag, 15. April 2002 16:32
An: Mario Weilguni
Cc: pgsql-hackers@postgresql.org
Betreff: Re: [HACKERS] Inefficient handling of LO-restore + Patch


"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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Importing Large Amounts of Data
Next
From: Tom Lane
Date:
Subject: Re: Inefficient handling of LO-restore + Patch