Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id D57AE476713 for ; Fri, 5 Apr 2002 11:30:06 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 1050295; Fri, 05 Apr 2002 08:30:08 -0800 From: "Josh Berkus" Subject: Re: 16 parameter limit To: Bruce Momjian , John Proctor Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Fri, 05 Apr 2002 08:30:08 -0800 Message-ID: In-Reply-To: <200204050240.g352e2W29464@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/68 X-Sequence-Number: 7333 Bruce, > Actually, I said it didn't come up much, but I know of several heavy > PL/pgSQL users who do have trouble with the 16 parameter limit, and I > am > looking into increasing it. If someone wants to do some legwork, go > ahead. I do think it needs to be increases. The lack of complains > makes it hard for me to advocate increasing it, especially if there > is a > disk space penalty, but personally, I do think it needs increasing. Personally, as a heavy user of PL/pgSQL procedures, I'm not sure you need to increase the *default* number of parameters. Postgres just needs to implement a parameter number change as part of a documented command-line compile-time option, i.e. "--with-parameters=32". Currently, increasing the number of parameters requires altering the C config files before compilation, a rather user-hostile process. I've raised this point 3 or 4 times on this list now, and have not seen a respons from you or Thomas on this suggestion. If I had the skills, I'd do it myself and upload the changes, but C is not my strong suit. Also, what is the practical maximum number of parameters? -Josh Berkus