| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | veem v <veema0000(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Moving to Postgresql database |
| Date: | 2024-01-16 18:06:38 |
| Message-ID: | 9513cef5-05e4-4ca1-ae9d-9fbf37c842c1@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/16/24 09:23, Dominique Devienne wrote:
> On Tue, Jan 16, 2024 at 6:10 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-01-16 18:09:21 | Re: Moving to Postgresql database |
| Previous Message | Ron Johnson | 2024-01-16 17:59:43 | Re: Moving to Postgresql database |