Date: Tue, 12 Apr 2005 11:47:54 -0400
From: Carlos Moreno <moreno@mochima.com>
Subject: Re: Update aborted if trigger function fails?
In-reply-to: <20050412151721.GA4291@phlogiston.dyndns.org>
To: pgsql-sql@postgresql.org
Message-id: <425BEDAA.5060802@mochima.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7)
	Gecko/20040616
References: <425ADE3F.1090206@mochima.com> <425B7920.4040002@archonet.com>
	<425BE162.6010501@mochima.com>
	<20050412151721.GA4291@phlogiston.dyndns.org>

Andrew Sullivan wrote:
> On Tue, Apr 12, 2005 at 10:55:30AM -0400, Carlos Moreno wrote:
> 
>>I guess the concern came up as result of a particular
>>situation, in which failing to properly process the
>>trigger function is not that crucial (I wanted to
>>update some additional information that is "optional",
>>and that can be reconstructed easily after discovering
>>that the trigger function had been failing).  But in
> 
> 
> If you can do some things asynchronously, and you don't care about
> them very much, then you can use LISTEN/NOTIFY to do such processing.

Thanks Andrew for the suggestion -- this may as well be
exactly the feature that I needed to begin with.  I'm
not familiar with the details, but I'll go right away
to dig through the docs.

Thanks!

Carlos
--