From: Hannu Krosing <hannu@tm.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Neil Conway <nconway@klamath.dyndns.org>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: josh@agliodbs.com, jproctor@prium.net, PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] [SQL] 16 parameter limit
Date: 16 Apr 2002 21:12:52 +0200
Message-ID: <1018984377.14960.28.camel@taru.tm.ee> (raw)
In-Reply-To: <9406.1018933293@sss.pgh.pa.us>
References: <Pine.LNX.4.30.0204160032190.834-100000@peter.localdomain>
<9406.1018933293@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: hannu@tm.ee, tgl@sss.pgh.pa.us, peter_e@gmx.net, nconway@klamath.dyndns.org, chriskl@familyhealth.com.au, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] [SQL] 16 parameter limit
In-Reply-To: <1018984377.14960.28.camel@taru.tm.ee>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox