X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6CCED9DC872 for ; Mon, 6 Mar 2006 22:39:16 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53497-06 for ; Mon, 6 Mar 2006 22:39:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0F8739DC809 for ; Mon, 6 Mar 2006 22:39:13 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k272dIKt012237; Mon, 6 Mar 2006 21:39:18 -0500 (EST) To: Richard Huxton cc: Emil Rachovsky , "pgsql-general@postgresql.org" , "pgsql-sql@postgresql.org" Subject: Re: problem with overloading the "coalesce" function In-reply-to: <440C1D34.6060308@archonet.com> References: <20060306111333.83983.qmail@web54306.mail.yahoo.com> <440C1D34.6060308@archonet.com> Comments: In-reply-to Richard Huxton message dated "Mon, 06 Mar 2006 11:29:56 +0000" Date: Mon, 06 Mar 2006 21:39:18 -0500 Message-ID: <12236.1141699158@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.112 required=5 tests=[AWL=0.112] X-Spam-Score: 0.112 X-Spam-Level: X-Archive-Number: 200603/231 X-Sequence-Number: 92096 Richard Huxton writes: > Hmm - looking at the source (and \df in psql) it seems the basic problem > is that COALESCE() isn't a function. If it were an ordinary function, it couldn't satisfy the property of not evaluating "unused" arguments ... regards, tom lane