Re: Moving to Postgresql database
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: veem v <veema0000@gmail.com>,
pgsql-general <pgsql-general@lists.postgresql.org>
Date: 2024-01-16T18:06:38Z
Lists: 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