From: | Jim Nasby <jim(dot)nasby(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Moving to Postgresql database |
Date: | 2024-01-16 18:36:13 |
Message-ID: | bd81fa1b-d00b-4c4f-9796-21509d8518c5@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2024-01-16 18:51:44 | Re: What should I expect when creating many logical replication slots? |
Previous Message | Ron Johnson | 2024-01-16 18:16:01 | Re: Moving to Postgresql database |