| From: | Anton Fedorov <datacompboy(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fwd: Non-cancellable queries |
| Date: | 2026-05-20 20:16:49 |
| Message-ID: | CACNOLFEJ27=d+ttW0e64fb=k720xCP9RWaL46PmwjTMtv6SfyQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 20 May 2026 at 22:11, Anton Fedorov <datacompboy(at)gmail(dot)com> wrote:
>
> On Wed, 20 May 2026 at 12:55, Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
>
>>
>> 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?
>
>
as extra bit here: MySQL fixed that as CVE-2026-21968
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2026-05-20 20:51:20 | Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade |
| Previous Message | Anton Fedorov | 2026-05-20 20:11:44 | Re: Fwd: Non-cancellable queries |