Re: FUNC_MAX_ARGS benchmarks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: FUNC_MAX_ARGS benchmarks
Date
Msg-id 14274.1028519785@sss.pgh.pa.us
Whole thread Raw
In response to Re: FUNC_MAX_ARGS benchmarks  (Joe Conway <mail@joeconway.com>)
Responses Re: FUNC_MAX_ARGS benchmarks
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> These are all with FUNC_MAX_ARGS = 16.

> #define NAMEDATALEN 32
> 2.7M    /opt/data/pgsql/data/base/1

> #define NAMEDATALEN 64
> 3.0M    /opt/data/pgsql/data/base/1

> #define NAMEDATALEN 128
> 3.8M    /opt/data/pgsql/data/base/1

Based on Joe's numbers, I'm kind of thinking that we should go for
FUNC_MAX_ARGS=32 and NAMEDATALEN=64 as defaults in 7.3.

Although NAMEDATALEN=128 would be needed for full SQL compliance,
the space penalty seems severe.  I'm thinking we should back off
until someone wants to do the legwork needed to make the name type
be truly variable-length.

Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: fate of CLUSTER command ?
Next
From: Joe Conway
Date:
Subject: Re: FUNC_MAX_ARGS benchmarks