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

From Hannu Krosing
Subject Re: [PATCHES] [SQL] 16 parameter limit
Date
Msg-id 1018984377.14960.28.camel@taru.tm.ee
Whole thread Raw
In response to Re: [PATCHES] [SQL] 16 parameter limit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 2002-04-16 at 07:01, Tom Lane wrote:
> 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.

Perhaps we could use the 16-th element as an indicator of 16-or-more
args. If it is 0 then there are <= 15 args if it is something else, then
this something else is hash of extra argument types that need to be
looked up separately. 

Of course we will need some way of resolving multiple hash matches.

--------------
Hannu




pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: [GENERAL] Testers needed ...
Next
From: Hannu Krosing
Date:
Subject: Re: multibyte support by default