MIME-Version: 1.0
References: <CALdQGgv_an=JdfkomND7sJcuAS1L5OmbFzhQa9qcW48syTXyKg@mail.gmail.com>
 <8fabad5643b3b10355c95e30f4e758c17640d0d0.camel@cybertec.at>
 <CALdQGgtteEQYNWhT80gNG3xSsjw+p1xDhFiG-+CUMXR9Gy=wBg@mail.gmail.com> <1643e5dbd663bbbc8f2458c8dab08da342529643.camel@cybertec.at>
In-Reply-To: <1643e5dbd663bbbc8f2458c8dab08da342529643.camel@cybertec.at>
From: Istvan Soos <istvan.soos@gmail.com>
Date: Sun, 8 Sep 2024 16:02:34 +0200
Message-ID: <CALdQGgvBTFq1mOHY1GZ2t-h1x0Tjw+-HuOkZshTD7GTHdWowwQ@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/CALdQGgvBTFq1mOHY1GZ2t-h1x0Tjw%2B-HuOkZshTD7GTHdWowwQ%40mail.gmail.com>
Precedence: bulk

On Sun, Sep 8, 2024 at 3:41=E2=80=AFPM Laurenz Albe <laurenz.albe@cybertec.=
at> wrote:
> You must be doing something wrong then, because it works:

And you are right, I was doing something wrong:

The combination of the change and the library internals triggered a
SET statement_timeout TO 3000; before the ROLLBACK was sent, and the
error message I got was not clear on which statement triggered it.

I'm sorry for the noise.

Btw. Is there any guideline on how to write the client libraries or
recommendations/tests that a client library should follow?

Thanks,
  Istvan