X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D5EDAD1DC20 for ; Fri, 28 Nov 2003 21:16:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 00176-07 for ; Fri, 28 Nov 2003 17:16:13 -0400 (AST) Received: from mail.hive.nj2.inquent.com (mc.carriermail.com [205.178.180.9]) by svr1.postgresql.org (Postfix) with SMTP id E3F50D1DC9E for ; Fri, 28 Nov 2003 17:04:16 -0400 (AST) Received: (qmail 25560 invoked from network); 28 Nov 2003 21:04:17 -0000 Received: from unknown (HELO ?10.0.2.5?) (216.208.117.7) by 205.178.180.9 with SMTP; 28 Nov 2003 21:04:17 -0000 Subject: Re: rules and return values question From: Rod Taylor To: Mujdat Pakkan Cc: pgsql-sql@postgresql.org In-Reply-To: References: Content-Type: text/plain Message-Id: <1070053467.40391.8.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 28 Nov 2003 16:04:28 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/331 X-Sequence-Number: 16146 > tables but it introduces too much overhead. In any case, we need the return > value (or an exception) from the function but there does not seem a way to > return it. Can't you use erreport() to return an exception message?