On 1/16/24 11:59 AM, Ron Johnson wrote:
> > Hi. One of the biggest pitfall of PostgreSQL, from the app-dev
> perspective,
> > is the fact any failed statement fails the whole
transaction, with
> > ROLLBACK as the only recourse.
>
> "SAVEPOINT establishes a new savepoint within the current
transaction.
>
>
> I wish it was that easy.
> I've been scared away from using them, after reading a few
articles...
> Also, that incurs extra round trips to the server, from the extra
commands.
The point was that '... with ROLLBACK as the only recourse.' is not
the
case. There is an alternative, whether you want to use it being a
separate question.
Performance-killing alternatives are not really altternatives.
What's the actual performance issue here?
I'm also wondering what the use case for constantly retrying errors is.
--
Jim Nasby, Data Architect, Austin TX
