MIME-Version: 1.0
References: 
 <CACNOLFFvMX521BZvPFyGwW=WOWk_1u-zqAm+j3BerYA6mx0jCA@mail.gmail.com>
 <CACNOLFGH_GPGXwzN23RXYbj3PaDxYKahHRGXnchCa7B=1TS7+w@mail.gmail.com>
 <3b02a3fe-bf62-4231-8ea8-5021f4846e2d@gmail.com>
 <CACNOLFGeVM+xdjd7ieR-kp+jV7gJOHxZdkqsaxOojRqiKakqKA@mail.gmail.com>
In-Reply-To: 
 <CACNOLFGeVM+xdjd7ieR-kp+jV7gJOHxZdkqsaxOojRqiKakqKA@mail.gmail.com>
From: Anton Fedorov <datacompboy@gmail.com>
Date: Wed, 20 May 2026 22:16:49 +0200
Message-ID: 
 <CACNOLFEJ27=d+ttW0e64fb=k720xCP9RWaL46PmwjTMtv6SfyQ@mail.gmail.com>
Subject: Re: Fwd: Non-cancellable queries
To: Andrei Lepikhov <lepihov@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000084e2630652457a83"
Archived-At: 
 <https://www.postgresql.org/message-id/CACNOLFEJ27%3Dd%2BttW0e64fb%3Dk720xCP9RWaL46PmwjTMtv6SfyQ%40mail.gmail.com>
Precedence: bulk

--00000000000084e2630652457a83
Content-Type: text/plain; charset="UTF-8"

On Wed, 20 May 2026 at 22:11, Anton Fedorov <datacompboy@gmail.com> wrote:

>
> On Wed, 20 May 2026 at 12:55, Andrei Lepikhov <lepihov@gmail.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

--00000000000084e2630652457a83
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, 20 May =
2026 at 22:11, Anton Fedorov &lt;<a href=3D"mailto:datacompboy@gmail.com">d=
atacompboy@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, 20 May 2026 =
at 12:55, Andrei Lepikhov &lt;<a href=3D"mailto:lepihov@gmail.com" target=
=3D"_blank">lepihov@gmail.com</a>&gt; wrote:</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><br></blockquote><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
Postgres code is aware of this situation and has a clear trade-off between<=
br>
performance and signal checking. Even if we fix this specific case, there a=
re<br>
multiple cycles in the code that might be expanded by a tricky query. So, c=
an<br>
you provide more context to define the problem&#39;s importance and scope s=
o we can<br>
determine whether this subject is actually important and should be fixed?</=
blockquote></div></div></blockquote><div><br></div><div>as extra bit here:=
=C2=A0 MySQL fixed that as=C2=A0CVE-2026-21968=C2=A0</div></div></div>

--00000000000084e2630652457a83--