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
