| From: | Carlos Moreno <moreno(at)mochima(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Update aborted if trigger function fails? |
| Date: | 2005-04-12 15:47:54 |
| Message-ID: | 425BEDAA.5060802@mochima.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. R. Van Hook | 2005-04-12 17:24:21 | max question |
| Previous Message | Dan Feiveson | 2005-04-12 15:18:56 | Re: Query runs very slowly in Postgres, but very fast in other DBMS |