Message-ID: <3b02a3fe-bf62-4231-8ea8-5021f4846e2d@gmail.com>
Date: Wed, 20 May 2026 12:55:24 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Fwd: Non-cancellable queries
To: Anton Fedorov <datacompboy@gmail.com>, pgsql-bugs@lists.postgresql.org
References: 
 <CACNOLFFvMX521BZvPFyGwW=WOWk_1u-zqAm+j3BerYA6mx0jCA@mail.gmail.com>
 <CACNOLFGH_GPGXwzN23RXYbj3PaDxYKahHRGXnchCa7B=1TS7+w@mail.gmail.com>
Content-Language: en-US
From: Andrei Lepikhov <lepihov@gmail.com>
In-Reply-To: 
 <CACNOLFGH_GPGXwzN23RXYbj3PaDxYKahHRGXnchCa7B=1TS7+w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/3b02a3fe-bf62-4231-8ea8-5021f4846e2d%40gmail.com>
Precedence: bulk

On 19/05/2026 22:44, Anton Fedorov wrote:
> You can run as many queries as you want; the queries sitting server-side,
> consuming CPU:
> image.png
> 
> The only way to kill them is to restart the server or wait almost indefinitely.
Yyou found the trick where the join list building routine consumes a lot of
resources.
Postgres code is aware of this situation and has a clear trade-off between
performance and signal checking. Even if we fix this specific case, there are
multiple cycles in the code that might be expanded by a tricky query. So, can
you provide more context to define the problem's importance and scope so we can
determine whether this subject is actually important and should be fixed?

-- 
regards, Andrei Lepikhov,
pgEdge