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

From Peter Eisentraut
Subject Re: [PATCHES] [SQL] 16 parameter limit
Date
Msg-id Pine.LNX.4.30.0204160032190.834-100000@peter.localdomain
Whole thread Raw
Responses Re: [PATCHES] [SQL] 16 parameter limit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> 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 ;-)

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.  This way procedures with
few arguments don't lose any performance but we could support an
"infinite" number of parameters easily.  It sounds kind of dumb, but
without some sort of break out of the fixed storage scheme we'll have this
argument forever.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Operators and schemas
Next
From: Tom Lane
Date:
Subject: Re: multibyte support by default