| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Anton Fedorov <datacompboy(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fwd: Non-cancellable queries |
| Date: | 2026-05-20 10:55:24 |
| Message-ID: | 3b02a3fe-bf62-4231-8ea8-5021f4846e2d@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2026-05-20 11:31:27 | Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always |
| Previous Message | Fujii Masao | 2026-05-20 10:03:23 | Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always |