public inbox for [email protected]
help / color / mirror / Atom feedFrom: Anton Fedorov <[email protected]>
To: Andrei Lepikhov <[email protected]>
Cc: [email protected]
Subject: Re: Fwd: Non-cancellable queries
Date: Wed, 20 May 2026 22:16:49 +0200
Message-ID: <CACNOLFEJ27=d+ttW0e64fb=k720xCP9RWaL46PmwjTMtv6SfyQ@mail.gmail.com> (raw)
In-Reply-To: <CACNOLFGeVM+xdjd7ieR-kp+jV7gJOHxZdkqsaxOojRqiKakqKA@mail.gmail.com>
References: <CACNOLFFvMX521BZvPFyGwW=WOWk_1u-zqAm+j3BerYA6mx0jCA@mail.gmail.com>
<CACNOLFGH_GPGXwzN23RXYbj3PaDxYKahHRGXnchCa7B=1TS7+w@mail.gmail.com>
<[email protected]>
<CACNOLFGeVM+xdjd7ieR-kp+jV7gJOHxZdkqsaxOojRqiKakqKA@mail.gmail.com>
On Wed, 20 May 2026 at 22:11, Anton Fedorov <[email protected]> wrote:
>
> On Wed, 20 May 2026 at 12:55, Andrei Lepikhov <[email protected]> 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
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], [email protected]
Subject: Re: Fwd: Non-cancellable queries
In-Reply-To: <CACNOLFEJ27=d+ttW0e64fb=k720xCP9RWaL46PmwjTMtv6SfyQ@mail.gmail.com>
* 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