On Fri, 2012-04-13 at 17:58 -0400, Eliot Gable 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?
1. Try using subtransactions
( http://www.postgresql.org/docs/9.1/static/sql-savepoint.html ). I
suggest releasing or rolling back the savepoints that you no longer need
because triggers can be executed many times.
2. You could have a separate connection that does the processing you
need, and use LISTEN/NOTIFY to alert the other connection that new data
is available to process.
Regards,
Jeff Davis
