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 fA71XJm44804 for ; Tue, 6 Nov 2001 20:33:19 -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 fA71Wuv10666; Tue, 6 Nov 2001 20:32:56 -0500 (EST) From: Bruce Momjian Message-Id: <200111070132.fA71Wuv10666@candle.pha.pa.us> Subject: Re: Can't find docs on Postgresql.conf In-Reply-To: <2774.1005093900@sss.pgh.pa.us> "from Tom Lane at Nov 6, 2001 07:45:00 pm" To: Tom Lane Date: Tue, 6 Nov 2001 20:32:56 -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/86 X-Sequence-Number: 5470 > Bruce Momjian writes: > > Doesn't it store in pg_proc as an array, which is of variable length? > > No, it's *fixed* length. Increasing FUNC_MAX_ARGS translates directly > to wasted space. Oh, I see it now, it is our old friend 'oidvector'. Now I remember modifying that when we changed from 8 to 16. I have modified the TODO to say: * Increase maximum number of function parameters if little wasted space We can address this during 7.3. and decide if it is worth it. Maybe it isn't. My calculations show a change of proc params from 16 to 32 would increase tuple length for pg_proc change from 180 to 244 or a 35% increase. -- 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