Postgres Pro
Downloads
Home   >   mailing lists

Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: - Mailing list pgsql-patches

From Peter Eisentraut
Subject Re: export FUNC_MAX_ARGS as a read-only GUC variable (was:
Date
Msg-id Pine.LNX.4.44.0312011950250.23890-100000@peter.localdomain
Whole thread Raw
In response to Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tree view 
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.

--
Peter Eisentraut   peter_e@gmx.net

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable
Next
From: Tom Lane
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)