public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Anthonin Bonnefoy <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Stmt timeout error can be sent after a CommandComplete
Date: Tue, 13 Jan 2026 12:30:54 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAO6_Xqqq2UAeRxrjxN9htu4RtvxJEWw4rLha4mPe5FOoZ2Byug@mail.gmail.com>
References: <CAO6_Xqqq2UAeRxrjxN9htu4RtvxJEWw4rLha4mPe5FOoZ2Byug@mail.gmail.com>

Anthonin Bonnefoy <[email protected]> writes:
> At the end of a command, disable_statement_timeout is called as the
> timeout applies to a specific command and a CommandComplete message is
> sent.
> However, it's possible for the stmt timeout to have been fired between
> the last message and the call to disable_statement_timeout. The
> timeout won't be active anymore, so disable_timeout will be skipped.
> However, the timeout is still queued, and the next call to
> CHECK_FOR_INTERRUPTS will process and generate a stmt timeout error.

I think this overlaps the discussion we're having over here:

https://www.postgresql.org/message-id/flat/CAGECzQQD5f9ce-D1v6vCTT94hG%3DJbGdTHuf8vQ%3DHBLz9T4dA1g%4...

I agree that this area is a bit buggy, but I think it's got more
problems than just this.

			regards, tom lane

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Stmt timeout error can be sent after a CommandComplete
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox