Re: Inefficient handling of LO-restore + Patch

From: "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)com>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inefficient handling of LO-restore + Patch
Date: 2002-04-15 14:46:41
Message-ID: D143FBF049570C4BB99D962DC25FC2D2178104@freedom.icomedias.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

And how about getting database internals via SQL-functions - e.g. getting BLCSIZE, LOBBLCSIZE?

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

"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?

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-04-15 15:37:20 Re: regexp character class locale awareness patch
Previous Message Michael Loftis 2002-04-15 14:33:20 Re: ANSI Compliant Inserts