Re: export FUNC_MAX_ARGS as a read-only GUC variable (was:
| От | Bruce Momjian |
|---|---|
| Тема | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
| Дата | |
| Msg-id | 200312010326.hB13QeW27947@candle.pha.pa.us обсуждение исходный текст |
| Ответ на | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: (Peter Eisentraut <peter_e@gmx.net>) |
| Список | 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@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
В списке pgsql-patches по дате отправления: