Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAP5c4m65060 for ; Sun, 25 Nov 2001 00:38:04 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fAP5c1c02964; Sun, 25 Nov 2001 00:38:02 -0500 (EST) To: Bruce Momjian cc: MindTerm , pgsql-sql@postgresql.org Subject: Re: How to create function with unspecified number of input parameters ? In-reply-to: <200111250529.fAP5T6G00259@candle.pha.pa.us> References: <200111250529.fAP5T6G00259@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Sun, 25 Nov 2001 00:29:05 -0500" Date: Sun, 25 Nov 2001 00:38:01 -0500 Message-ID: <2961.1006666681@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/355 X-Sequence-Number: 5737 Bruce Momjian writes: > Is this a TODO item? Dunno. I certainly wouldn't be in favor of unspecified arguments (like ANSI C's "..." construct), because it'd totally destroy our datatype resolution mechanism. Optional arguments might work, but it needs some careful thought. regards, tom lane