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

From Philip Warner
Subject Re: Inefficient handling of LO-restore + Patch
Date
Msg-id 5.1.0.14.0.20020424155702.02a2f3c0@mail.rhyme.com.au
Whole thread Raw
In response to Inefficient handling of LO-restore + Patch  ("Mario Weilguni" <mario.weilguni@icomedias.com>)
Responses Re: Inefficient handling of LO-restore + Patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 16:46 15/04/02 +0200, Mario Weilguni wrote:
>And how about getting database internals via SQL-functions - e.g. getting 
>BLCSIZE, LOBBLCSIZE?

ISTM that there would be some merit in making a selection of compile-time 
options available via SQL. Is this worth considering?





pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Vote on SET in aborted transaction
Next
From: Lincoln Yeoh
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE