Re: in failed sql transaction
| От | Gurjeet Singh |
|---|---|
| Тема | Re: in failed sql transaction |
| Дата | |
| Msg-id | 65937bea0609260312j1aa71771nf5b6eb4b963d7b09@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: in failed sql transaction (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | 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>
--
gurjeet@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com
<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@sss.pgh.pa.us> wrote:
Ralf Wiebicke <ralf.wiebicke@exedio.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@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com
В списке pgsql-general по дате отправления: