I know savepoints are supported by PostgreSQL, but what about existing/legacy code that has tons of lines that rely on the behavior of other DB engines?
Would you ask programmers to put a savepoint / release savepoint around each SQL statement inside a TX?
Seb
From: David Rowley <dgrowleyml@gmail.com> Sent: Monday, April 4, 2022 1:44 PM To: Sebastien Flaesch <sebastien.flaesch@4js.com> Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org> Subject: Re: Transaction and SQL errors
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
On Mon, 4 Apr 2022 at 23:33, Sebastien Flaesch <sebastien.flaesch@4js.com> wrote: > Any arguments I could give to programmers? Maybe: > "You better replay all SQL of the whole transaction... (and make them as short as possible!)" > ?