Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fA82agm37891 for ; Wed, 7 Nov 2001 21:36:42 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id fA82a0W25553; Wed, 7 Nov 2001 21:36:00 -0500 (EST) From: Bruce Momjian Message-Id: <200111080236.fA82a0W25553@candle.pha.pa.us> Subject: Re: Can't find docs on Postgresql.conf In-Reply-To: <20011107174055.A11558@cc.usu.edu> "from Roberto Mello at Nov 7, 2001 05:40:55 pm" To: Roberto Mello Date: Wed, 7 Nov 2001 21:36:00 -0500 (EST) CC: Tom Lane , Josh Berkus , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200111/120 X-Sequence-Number: 5504 > On Tue, Nov 06, 2001 at 07:21:09PM -0500, Bruce Momjian wrote: > > > > I was talking to Ben Adida last week (OpenACS) and he mentioned they are > > having problems with the limit at 16, and it seems Josh is as well. Ben > > is doing some object-oriented function mechanism, and you know how that > > can eat parameters. Seems we should increase to 24 or 32. Is there a > > downside to the increase. I can't even imagine a performance hit. > > Indeed we (at OpenACS) could use more parameters. > > We are porting a zillion Oracle PL/SQL functions to Postgres, and in > Oracle you can have optional parameters and default values. In PostgreSQL > we have to overload functions to make up for the possible combinations. > > In this process, sometimes we run out of parameters and have to submit to > more, errr, creative ways to get the job done. Good. Will 24 params be enough for you? -- 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