Re: export FUNC_MAX_ARGS as a read-only GUC variable (was:
От | Peter Eisentraut |
---|---|
Тема | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
Дата | |
Msg-id | Pine.LNX.4.44.0311302007030.11144-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)
Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
Список | pgsql-patches |
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. > I was intending to propose that we also export the following as > read-only variables: > * NAMEDATALEN And this as well. > * BLCKSZ Why would anyone be interested in that? > * integer-vs-float datetime flag Here we should really decide on one representation in the near term. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-patches по дате отправления: