Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 7E380475858 for ; Thu, 4 Apr 2002 21:40:10 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g352e2W29464; Thu, 4 Apr 2002 21:40:02 -0500 (EST) From: Bruce Momjian Message-Id: <200204050240.g352e2W29464@candle.pha.pa.us> Subject: Re: 16 parameter limit In-Reply-To: <200204030211.g332BLa15946@slxmail01.prium.net> To: John Proctor Date: Thu, 4 Apr 2002 21:40:02 -0500 (EST) Cc: pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200204/62 X-Sequence-Number: 7327 John Proctor wrote: > > RE: 16 parameter limit > > There was a message posted in March regarding this. Bruce replied that this > issue did not come up often. However, I think there is more to it than > that. I think one reason that it does not come up is because most Oracle > DBAs are not going to dig through mailing lists and take the time to post > questions. Once they discover that PL/pgSQL != PL/SQL they just move on. 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. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026