From 8396d74d111ea4e57114a2cc84c9f7cd2fa6ed61 Mon Sep 17 00:00:00 2001
From: Sergei Golubchik <serg@mariadb.org>
Date: Fri, 16 Oct 2026 11:03:08 +0200
Subject: [PATCH] ER_OUT_OF_SORTMEMORY should not be ME_ERROR_LOG+ME_FATAL

it's not OOM, it's "filesort requires more memory than a user specified
session local limit". Not a hardware limitation, but something
an unprivileged user configured in her own session (so, shouldn't
be ME_ERROR_LOG). And unlike true low-memory situation this error
condition doesn't affect following statements (so, shouldn't be ME_FATAL)
---
 sql/filesort.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sql/filesort.cc b/sql/filesort.cc
index 0f4d15a1fe1..a2ea03698df 100644
--- a/sql/filesort.cc
+++ b/sql/filesort.cc
@@ -339,7 +339,7 @@ SORT_INFO *filesort(THD *thd, TABLE *table, Filesort *filesort,
     }
     if (memory_available < min_sort_memory)
     {
-      my_error(ER_OUT_OF_SORTMEMORY,MYF(ME_ERROR_LOG + ME_FATAL));
+      my_error(ER_OUT_OF_SORTMEMORY, MYF(0));
       goto err;
     }
     tracker->report_sort_buffer_size(sort->sort_buffer_size());