From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: in failed sql transaction |
Date: | 2006-09-26 10:12:55 |
Message-ID: | 65937bea0609260312j1aa71771nf5b6eb4b963d7b09@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks a lot for the pointer.... This is exactly what I have been looking
for.
<from_docs>
The on_error_rollback-on mode works by issuing an implicit SAVEPOINT for
you, just before each command that is in a transaction block, and rolls back
to the savepoint on error.
</from_docs>
On 9/26/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Ralf Wiebicke <ralf(dot)wiebicke(at)exedio(dot)com> writes:
> > I finally used savepoints to get what I want.
> > However I don't like this very much.
>
> Have you experimented with psql's ON_ERROR_ROLLBACK setting?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
gurjeet(at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Peter | 2006-09-26 10:21:52 | strange sql issue |
Previous Message | Martijn van Oosterhout | 2006-09-26 09:10:11 | Re: Replication and PITR |