| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 03:26:40 |
| Message-ID: | 200312010326.hB13QeW27947@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > One could make a good case that INDEX_MAX_KEYS should be exported along
> > with FUNC_MAX_ARGS, rather than letting people write client code that
> > assumes they are the same.
>
> You can determine these values by looking into the system catalogs.
How, count? Seems we should give an easy API.
> > I was intending to propose that we also export the following as
> > read-only variables:
> > * NAMEDATALEN
>
> And this as well.
Again, why not make it easy.
> > * BLCKSZ
>
> Why would anyone be interested in that?
Performance/admin tools might need this --- you need it to get the disk
size based on the number of pages recorded in pg_class.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Uwe C. Schroeder | 2003-12-01 03:46:51 | Bug or Feature - plpgsql odity |
| Previous Message | Barbara Lindsey | 2003-12-01 02:58:06 | Pg module for Perl |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-12-01 03:55:26 | GUC descriptions of SHOW |
| Previous Message | Bruce Momjian | 2003-12-01 02:54:40 | Re: clock_timestamp() and transaction_timestamp() function |