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

From Tom Lane
Subject Re: [PATCHES] [SQL] 16 parameter limit
Date
Msg-id 9406.1018933293@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] [SQL] 16 parameter limit  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCHES] [SQL] 16 parameter limit  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [PATCHES] [SQL] 16 parameter limit  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> How about this:  We store the first 16 parameters in some fixed array for
> fast access like now, and when you have more than 16 then 17 and beyond
> get stored in some variable array in pg_proc.

<<itch>>  What's this going to cost us in the function lookup code paths?

If we can do it with little or no performance cost (at least for the
"normal case" of fewer-than-N parameters) then I'm all ears.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Firebird 1.0 released
Next
From: Curt Sampson
Date:
Subject: Re: Importing Large Amounts of Data