| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Alex <alex(at)meerkatsoft(dot)com>, Lada 'Ray' Lostak <ray(at)unreal64(dot)net>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
| Date: | 2003-12-01 18:51:14 |
| Message-ID: | Pine.LNX.4.44.0312011950250.23890-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-01 18:54:47 | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) |
| Previous Message | Greg Stark | 2003-12-01 18:49:30 | Undropping a column? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-01 18:54:47 | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) |
| Previous Message | Joe Conway | 2003-12-01 18:32:13 | Re: export FUNC_MAX_ARGS as a read-only GUC variable |