Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> There was just a discussion a few days ago about the page size for large
>> objects, for which the correct answer was "BLCKSZ/4" IIRC. Whether
>> people actually *should* care about the page size of large objects I
>> dunno, but the fact is some of them *do* care.
> Maybe we should provide specific functions to access this information, so
> client applications don't have to hardcode these formulas.
That's exactly what this thread is about: current_setting() is the
proposed access function ...
I'm not convinced that large object pagesize is interesting enough to
deserve its own GUC variable, but if someone wanted to make that case
I'm certainly open to listening.
regards, tom lane