Re: export FUNC_MAX_ARGS as a read-only GUC variable - Mailing list pgsql-patches

From Joe Conway
Subject Re: export FUNC_MAX_ARGS as a read-only GUC variable
Date
Msg-id 3FCADE3B.2040005@joeconway.com
Whole thread Raw
In response to Re: export FUNC_MAX_ARGS as a read-only GUC variable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: export FUNC_MAX_ARGS as a read-only GUC variable
List 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



pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: ISO 8601 "Time Intervals" of the "format with time-unit
Next
From: Tom Lane
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable