transaction error handling - Mailing list pgsql-admin

From Kasia Tuszynska
Subject transaction error handling
Date
Msg-id 232B5217AD58584C87019E8933556D11036BDE58EB@redmx2.esri.com
Whole thread Raw
In response to Re: Repeatable crash in pg_dump (with -d2 info)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: transaction error handling  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: transaction error handling  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: transaction error handling  (Rob Richardson <RDRichardson@rad-con.com>)
List 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 by date:

Previous
From: David Schnur
Date:
Subject: Re: Repeatable crash in pg_dump (with -d2 info)
Next
From: Craig James
Date:
Subject: Deadlock on "select ... for update"?