From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
---|---|
To: | Paramveer(dot)Singh(at)trilogy(dot)com |
Cc: | "pgSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: resilient transactions |
Date: | 2004-09-07 12:00:57 |
Message-ID: | 93EC4232-00C5-11D9-8F3E-000D9366F0C4@torgo.978.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sep 7, 2004, at 3:35 AM, Paramveer(dot)Singh(at)trilogy(dot)com wrote:
> Hi all!
> Apologies for sending this mail but some time back there was a thread
> on
> supporting resilient transactions - i.e. transactions which do not roll
> back if one query in 100 fails.
transactions can either entirely succeed or entirely fail, there is no
"sometimes". Any discussion or even patches that do change that will
be rejected immediately (Well, I'm simply assuming they will. I think
myself and many others would be mighty surprised if a patch like that
got applied!)
PG 8.0 introduces a feature called savepoints which allows you to trap
errors inside a transaction (and also rollback parts of the
transaction, etc.) You may want to look into that.
http://developer.postgresql.org/docs/postgres/sql-savepoint.html
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Thomas | 2004-09-07 13:11:50 | Re: ERROR: canceling query due to user request |
Previous Message | Oliver Elphick | 2004-09-07 11:56:46 | Re: changing the password of postres |