Received: from klamath.dyndns.org (CPE002078144ae0.cpe.net.cable.rogers.com [24.102.202.35]) by postgresql.org (Postfix) with ESMTP id 5FA95475A59 for ; Tue, 16 Apr 2002 12:04:35 -0400 (EDT) Received: from jiro (jiro [192.168.40.7]) by klamath.dyndns.org (Postfix) with SMTP id 3B8F4700C; Tue, 16 Apr 2002 12:04:40 -0400 (EDT) Date: Tue, 16 Apr 2002 12:04:37 -0400 From: Neil Conway To: "John Proctor" Cc: josh@agliodbs.com, peter_e@gmx.net, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-patches@postgresql.org Subject: Re: [SQL] 16 parameter limit Message-Id: <20020416120437.3e68fcff.nconway@klamath.dyndns.org> In-Reply-To: <200204160446.g3G4kha06293@slxmail01.prium.net> References: <200204160446.g3G4kha06293@slxmail01.prium.net> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200204/178 X-Sequence-Number: 3693 On Mon, 15 Apr 2002 23:49:21 -0500 "John Proctor" wrote: > However, none of the above is of any value if the performance penalty is > large. And PL/pgSQL needs much more that just the param number increased. John, Could you elaborate on what enhancements you'd like to see in PL/pgSQL? Cheers, Neil -- Neil Conway PGP Key ID: DB3C29FC