Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e5SICN121410 for ; Wed, 28 Jun 2000 14:12:23 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id OAA16715; Wed, 28 Jun 2000 14:12:04 -0400 (EDT) To: Bruce Momjian cc: Andrey , pgsql-sql@postgresql.org Subject: Re: Procedures cannot take more than 16 arguments In-reply-to: <200006281751.NAA20819@candle.pha.pa.us> References: <200006281751.NAA20819@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Wed, 28 Jun 2000 13:51:01 -0400" Date: Wed, 28 Jun 2000 14:12:04 -0400 Message-ID: <16712.962215924@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/264 >> Does anyone know the way of sending more than 16 parameters to function? Change the relevant parameters in config.h (there are two), rebuild, reinstall, initdb. Bruce Momjian writes: > In 7.0, I could have sworn I had an #ifdef to go up to 32, but I don't > see it anymore. If you're talking about that switch statement in fmgr.c, I don't think it needs to support more than 16 in the new fmgr --- there certainly is no reason to tie it directly to FUNC_MAX_ARGS. The switch only applies to calling old-style builtin or dynamically-loaded old-style C functions. There aren't any old-style builtin functions left with more than 3 args, and if there's someone out there with a C function that takes more than 16 he'd be well advised to convert it to newstyle anyway. (He could only have written such a function since 7.0 release ... the historical limit was just 8, so I think the oldstyle cases beyond 8 are likely to be dead code anyhow ... not much point in cluttering the backend with more cases.) I think I need to change the config.h comment that goes with MAX_FUNC_ARGS. regards, tom lane