transaction error handling
От | Kasia Tuszynska |
---|---|
Тема | transaction error handling |
Дата | |
Msg-id | 232B5217AD58584C87019E8933556D11036BDE58EB@redmx2.esri.com обсуждение исходный текст |
Ответ на | Re: Repeatable crash in pg_dump (with -d2 info) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: transaction error handling
Re: transaction error handling Re: transaction error handling |
Список | pgsql-admin |
Hi Everybody, This is an architectural question. I am testing on Postgres 9.0.2 on windows and linux(suse, rhel, ubuntu) I want to make sure that I have the correct understanding of the Postgres architecture and would like to enquire if thereare any plans to change it. Comparing Oracle and Postgres from the perspective of error handling on the transaction level I observed the following: Oracle: Begin transaction Insert - no error Implicit savepoint Insert - error raised Implicit rollback to the savepoint, no transaction loss, error raised on the insert statement that errored out. End transaction, implicit commit, with the single error free insert. Postgres: Begin transaction Insert - no error Insert - error raised Transaction loss = no implicit rollback to the single error free insert. Is this a correct interpretation of the Postgres transaction error handling? If so, are there any changes being considered, or perhaps already implemented? Sincerely, Kasia
В списке pgsql-admin по дате отправления: