Ravi Krishna wrote:
> I have hardly used savepoints in any application, but if I understand it correctly, isn't it something which is
typicallyused
> in a persistent connection. I wonder how it is applicable in a web based stateless application like Amazon.com,
unless
> even web based application have database level state.
I have seen people use savepoints in PostgreSQL to emulate Oracle's
"statement rollback" behavior: If a statement fails, only the statement
is undone, but the transaction continues.
If you insert a savepoint before *every* statement in a transaction,
you can get a similar behavior in PostgreSQL, but the performance will
suck.
Perhaps that is what happened in this case.
Of course the correct solution is to redesign and use savepoints only
where you *expect* an error, or at least batch a number of statements
with each savepoint.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
