Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id F2F7B474E42 for ; Tue, 16 Apr 2002 00:06:42 -0400 (EDT) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1371993; Mon, 15 Apr 2002 21:06:44 -0700 From: "Josh Berkus" Subject: Re: [SQL] 16 parameter limit To: Peter Eisentraut , Bruce Momjian Cc: Tom Lane , Josh Berkus , John Proctor , PostgreSQL-patches X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Mon, 15 Apr 2002 21:06:44 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/173 X-Sequence-Number: 3688 Peter, > If you want to increase it, let's just increase it and not add any > more > configure options. If someone wants more than 32 then we really need > to > start talking about design issues. Actually, many Oracle DBAs use functions/procedures with up to 300 parameters. If we want them to take PostgreSQL seriously as an alternative to Oracle, we need to be able to accommodate that, at the very least through an accessable configure-time option. Also, this is a very frequent request on the SQL list. The fact that currently the defualt is 16 and pg_config.h is not documented anywhere, is rather unfriendly to developers who like to use their functions as pseudo-middleware. John, please speak up here so the core team knows this isn't "just me." -Josh Berkus