Re: Moving to Postgresql database
От | Adrian Klaver |
---|---|
Тема | Re: Moving to Postgresql database |
Дата | |
Msg-id | 9513cef5-05e4-4ca1-ae9d-9fbf37c842c1@aklaver.com обсуждение исходный текст |
Ответ на | Re: Moving to Postgresql database (Dominique Devienne <ddevienne@gmail.com>) |
Список | pgsql-general |
On 1/16/24 09:23, Dominique Devienne wrote: > On Tue, Jan 16, 2024 at 6:10 PM Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > Technically, it's still a ROLLBACK, so that is indeed the only recourse. Actually ROLLBACK TO: https://www.postgresql.org/docs/current/sql-rollback-to.html You would get a different outcome with just a plain ROLLBACK. > But sure, I take your point, you can emulate statement-level (implicit) > rollback > via an explicit SAVEPOINT, and ROLLBACK to the savepoint instead. > > But my point remains, that something like what that extension does should > be an option of PostgreSQL itself, not an extension. --DD > > PS: I'd also be happy to hear why it's not, or won't be, on technical terms. -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: