X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 71CC714B287E
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon,  9 Aug 2004 13:53:40 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 89042-03
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon,  9 Aug 2004 16:53:34 +0000 (GMT)
Received: from tht.net (vista.tht.net [216.126.88.2])
	by svr1.postgresql.org (Postfix) with ESMTP id F3F2914B287B
	for <pgsql-sql@postgresql.org>; Mon,  9 Aug 2004 13:53:07 -0300 (ADT)
Received: from [134.22.70.202] (dyn-70-202.tor.dsl.tht.net [134.22.70.202])
	by tht.net (Postfix) with ESMTP
	id A2A6D76BA5; Mon,  9 Aug 2004 12:52:57 -0400 (EDT)
Subject: Re: Exception handling from trigger
From: Rod Taylor <pg@rbt.ca>
To: Vlad Dimitriu <vlad.dimitriu@base.ro>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <4117AA90.9080704@base.ro>
References: <4117AA90.9080704@base.ro>
Content-Type: text/plain
Message-Id: <1092070373.799.50.camel@jester>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Mon, 09 Aug 2004 12:52:54 -0400
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200408/63
X-Sequence-Number: 18560

> Is this way of handling exceptions possible in postgres ?
> If so, what is the normal way to handle this exceptions, from a
> plpgsql/trigger(rule??) perspective ?

8.0 should allow you to do this. 7.4 you need to perform your own checks
and catch whether they succeed or fail.