Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 278D4475BB7 for ; Tue, 16 Apr 2002 00:50:20 -0400 (EDT) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1372043; Mon, 15 Apr 2002 21:50:21 -0700 From: "Josh Berkus" Subject: Re: [SQL] 16 parameter limit To: Tom Lane , Neil Conway Cc: "Christopher Kings-Lynne" , peter_e@gmx.net, pgman@candle.pha.pa.us, josh@agliodbs.com, jproctor@prium.net, pgsql-patches@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Mon, 15 Apr 2002 21:50:21 -0700 Message-ID: In-Reply-To: <9110.1018930411@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/175 X-Sequence-Number: 3690 Tom, > Still, I do not really see the value of adding a configure argument. > Anyone who can't figure out how to tweak this in pg_config.h is > probably > not ready to run a non-default configuration anyhow. I disagree *very* strongly. Given that the documentation on pg_config.h was removed from the idocs and that Pater has made noises about removing pg_config.h entirely, it is not a substitute for command-line configure options. > If the consensus is to raise the default from 16 to 32, I won't > object. > Beyond that, I'd start asking questions about who's measured the > performance hit and what they found. If you can suggest a reasonable test, I will test this at 32, 64, 128 and 256 parameters to settle this issue. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco