Re: Preventing an 'after' trigger from causing rollback on error - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Preventing an 'after' trigger from causing rollback on error
Date
Msg-id CAOR=d=33VO0t4BLAcaf=qudCbTzvwJt39g702V4MuNbmCKR=fg@mail.gmail.com
Whole thread Raw
In response to Preventing an 'after' trigger from causing rollback on error  (Eliot Gable <egable+pgsql-general@gmail.com>)
List pgsql-general
On Fri, Apr 13, 2012 at 3:58 PM, Eliot Gable
<egable+pgsql-general@gmail.com> wrote:
> Is there any way I can stop a trigger which fires after a row is inserted
> into a table from causing a rollback of the entire transaction if something
> goes wrong?

Take look here:

http://www.postgresql.org/docs/9.0/static/plpgsql-porting.html

Specifically the part about:

BEGIN
        INSERT INTO cs_jobs (job_id, start_stamp) VALUES (v_job_id, now());
    EXCEPTION
        WHEN unique_violation THEN (2)
            -- don't worry if it already exists
    END;

pgsql-general by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Preventing an 'after' trigger from causing rollback on error
Next
From: leaf_yxj
Date:
Subject: how to list all the schema and the privileges which is granted to users.THanks.