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 fA70LVm42522 for ; Tue, 6 Nov 2001 19:21:32 -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 fA70L9O03486; Tue, 6 Nov 2001 19:21:09 -0500 (EST) From: Bruce Momjian Message-Id: <200111070021.fA70L9O03486@candle.pha.pa.us> Subject: Re: Can't find docs on Postgresql.conf In-Reply-To: <2435.1005092279@sss.pgh.pa.us> "from Tom Lane at Nov 6, 2001 07:17:59 pm" To: Tom Lane Date: Tue, 6 Nov 2001 19:21:09 -0500 (EST) CC: 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/83 X-Sequence-Number: 5467 > Bruce Momjian writes: > > The number of params and the length of identifiers are two things we > > should increase in 7.3. > > > In TODO we now have: > > > * Increase identifier length (NAMEDATALEN) if small performance hit > > * Increase maximum number of function parameters > > We already *did* increase the standard max number of function > parameters, from 8 to 16, and that was just a couple or three versions > back. I don't recall hearing any groundswell of complaints to evidence > that very many people need it set higher. 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. Comments? -- 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