| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: export FUNC_MAX_ARGS as a read-only GUC variable |
| Date: | 2003-12-01 06:22:51 |
| Message-ID: | 3FCADE3B.2040005@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-patches |
Tom Lane wrote:
> Perhaps the GUC variable name should be max_name_len or some such.
>
> Also, should func_max_args and index_max_keys become max_func_args and
> max_index_keys?
That sounds good to me:
-[ RECORD 3 ]----------------------------------------------
name | max_func_args
setting | 32
-[ RECORD 4 ]----------------------------------------------
name | max_index_keys
setting | 32
-[ RECORD 5 ]----------------------------------------------
name | max_name_len
setting | 63
I'll finish up the docs and commit this tomorrow, barring strong
complaints. It will require an initdb -- should I hold off for other
pending changes also requiring initdb?
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-01 06:27:03 | Re: export FUNC_MAX_ARGS as a read-only GUC variable |
| Previous Message | Peter Eisentraut | 2003-12-01 06:20:21 | Re: ISO 8601 "Time Intervals" of the "format with time-unit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-01 06:27:03 | Re: export FUNC_MAX_ARGS as a read-only GUC variable |
| Previous Message | Peter Eisentraut | 2003-12-01 06:20:21 | Re: ISO 8601 "Time Intervals" of the "format with time-unit |