Re: [SQL] 16 parameter limit - Mailing list pgsql-patches

From Tom Lane
Subject Re: [SQL] 16 parameter limit
Date
Msg-id 9110.1018930411@sss.pgh.pa.us
Whole thread Raw
In response to Re: [SQL] 16 parameter limit  (Neil Conway <nconway@klamath.dyndns.org>)
Responses Re: [SQL] 16 parameter limit  ("Josh Berkus" <josh@agliodbs.com>)
List pgsql-patches
Neil Conway <nconway@klamath.dyndns.org> writes:
> My vote is to set the default # of function args to some
> reasonable default (32 sounds good), and leave it at that.

Bear in mind that s/32/16/ gives you the exact state of the discussion
when we raised the limit from 8 to 16 ;-)

Still, I do not really see the value of adding a configure argument.
Anyone who can't figure out how to tweak this in pg_config.h is probably
not ready to run a non-default configuration anyhow.

If the consensus is to raise the default from 16 to 32, I won't object.
Beyond that, I'd start asking questions about who's measured the
performance hit and what they found.

On the NAMEDATALEN part of the argument: SQL92 clearly expects that
NAMEDATALEN should be 128.  But the first report of the performance
cost looked rather grim.  Has anyone retried that experiment since
we tweaked hashname to not hash all the trailing zeroes?

            regards, tom lane

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [SQL] 16 parameter limit
Next
From: Peter Eisentraut
Date:
Subject: Re: ANSI Compliant Inserts