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
