Re: Moving to Postgresql database

Поиск
Список
Период
Сортировка
Искать
От
Jim Nasby
Тема
Re: Moving to Postgresql database
Дата
Msg-id
bd81fa1b-d00b-4c4f-9796-21509d8518c5@gmail.com
Ответ на
Список
Дерево обсуждения
Moving to Postgresql database veem v <veema0000@gmail.com>
Re: Moving to Postgresql database Justin Clift <justin@postgresql.org>
Re: Moving to Postgresql database Henrique Lima <henrique.sglima@gmail.com>
Re: Moving to Postgresql database Dominique Devienne <ddevienne@gmail.com>
Re: Moving to Postgresql database Adrian Klaver <adrian.klaver@aklaver.com>
Re: Moving to Postgresql database Dominique Devienne <ddevienne@gmail.com>
Re: Moving to Postgresql database Adrian Klaver <adrian.klaver@aklaver.com>
Re: Moving to Postgresql database Dominique Devienne <ddevienne@gmail.com>
Re: Moving to Postgresql database Tom Lane <tgl@sss.pgh.pa.us>
Re: Moving to Postgresql database Dominique Devienne <ddevienne@gmail.com>
Re: Moving to Postgresql database Tom Lane <tgl@sss.pgh.pa.us>
Re: Moving to Postgresql database Jim Nasby <jim.nasby@gmail.com>
Re: Moving to Postgresql database Adrian Klaver <adrian.klaver@aklaver.com>
Re: Moving to Postgresql database Ron Johnson <ronljohnsonjr@gmail.com>
Re: Moving to Postgresql database Jim Nasby <jim.nasby@gmail.com>
Re: Moving to Postgresql database Adrian Klaver <adrian.klaver@aklaver.com>
Re: Moving to Postgresql database Ron Johnson <ronljohnsonjr@gmail.com>
Re: Moving to Postgresql database Merlin Moncure <mmoncure@gmail.com>
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



В списке pgsql-general по дате отправления
От: Ron Johnson
Дата:
От: Jim Nasby
Дата:
FAQ