Re: Transaction and SQL errors - Mailing list pgsql-general

From Sebastien Flaesch
Subject Re: Transaction and SQL errors
Date
Msg-id DBAP191MB128948A1A03136C661483EBAB0E59@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Transaction and SQL errors  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Transaction and SQL errors  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
Hi David,

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!)"
> ?

There are SAVEPOINTs [1].

David

[1] https://urldefense.com/v3/__https://www.postgresql.org/docs/current/sql-savepoint.html__;!!I_DbfM1H!SJaCAE7hUHxRte8uMaa9RB8byL3QsmxkBRzk9POp0N8sLvjhpL5AWoiH-7MEuTkZMcrl$

pgsql-general by date:

Previous
From: Sebastien Flaesch
Date:
Subject: Re: Transaction and SQL errors
Next
From: Ravi Krishna
Date:
Subject: Re: Select .... where id not in (....) returns 0 incorrectly