From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Update aborted if trigger function fails?
Date: Tue, 12 Apr 2005 11:17:21 -0400
Message-ID: <20050412151721.GA4291@phlogiston.dyndns.org> (raw)
In-Reply-To: <425BE162.6010501@mochima.com>
References: <425ADE3F.1090206@mochima.com>
<425B7920.4040002@archonet.com>
<425BE162.6010501@mochima.com>
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.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Information security isn't a technological problem. It's an economics
problem.
--Bruce Schneier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Update aborted if trigger function fails?
In-Reply-To: <20050412151721.GA4291@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox