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

From Peter Eisentraut
Subject Re: export FUNC_MAX_ARGS as a read-only GUC variable (was:
Date
Msg-id Pine.LNX.4.44.0311302007030.11144-100000@peter.localdomain
Whole thread Raw
In response to Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses 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:  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)
Next
From: Tom Lane
Date:
Subject: Re: Problem with dblink