MIME-Version: 1.0
References: <CALdQGgv_an=JdfkomND7sJcuAS1L5OmbFzhQa9qcW48syTXyKg@mail.gmail.com>
 <8fabad5643b3b10355c95e30f4e758c17640d0d0.camel@cybertec.at>
In-Reply-To: <8fabad5643b3b10355c95e30f4e758c17640d0d0.camel@cybertec.at>
From: Istvan Soos <istvan.soos@gmail.com>
Date: Sun, 8 Sep 2024 15:01:51 +0200
Message-ID: <CALdQGgtteEQYNWhT80gNG3xSsjw+p1xDhFiG-+CUMXR9Gy=wBg@mail.gmail.com>
Subject: Re: How to cleanup transaction after statement_timeout aborts a query?
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CALdQGgtteEQYNWhT80gNG3xSsjw%2Bp1xDhFiG-%2BCUMXR9Gy%3DwBg%40mail.gmail.com>
Precedence: bulk

On Sun, Sep 8, 2024 at 1:19=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.=
at> wrote:
> ROLLBACK and COMMIT are working: they end the transaction.

I have this reproduction test, and ROLLBACK does fail:
https://github.com/isoos/postgresql-dart/pull/363/files#diff-4547e49b04ec82=
80fb8f4f1ebf695b77f9a2d9a4ac9bcfd685bcd570a46baa80R122

I've checked and nothing else is sent on the protocol, yet, for the
rollback statement it gets the 25P02 error.

> It is the atomicity guarantee of database transactions: either all statem=
ents
> succeed, or all fail.

Yeah, I thought so, that's why I'm struggling to see what's missing.

> To handle the failure of a statement while allowing the transaction to pr=
oceed,
> you can use savepoints.  But be warned: don't even think of setting a sav=
epoint
> before each statement.  That would affect statement performance severely.

As the writer of the client library, I don't have the luxury of
telling users they need to change their way, hence I'm looking for any
pointer on the protocol level.

Thanks,
  Istvan