Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
11.4.2
-
None
-
MariaDB 11.4.2; Windows 10 x64 22h2 (Because I like a working computer); WAMP
-
Not for Release Notes
Description
I created a test SQL query to do some basic counting for internal debugging purposes (confirmed duplicates) and it turned out to be a very long running query that I stopped tracking about after five minutes.
So I simply wanted to update the configuration file to automatically stop the execution of excessively long-running queries.
I did manage to get it working through the CLI call set in the Windows registry, here is a minimized version of that call:
"C:\MariaDB\bin\mysqld.exe" "--defaults-file=C:\MariaDB\data\my.ini" "--max_statement_time=4" "MariaDB"
|
However setting max_statement_time in my my.ini configuration file fails! Additionally it is not documented for the configuration file here: https://mariadb.com/docs/server/ha-and-performance/optimization-and-tuning/system-variables/server-system-variables#max_statement_time
Windows installs will ultimately fail sooner or later and have to be reinstalled. That is why the internal configuration file is far superior. Just like blocking a number on a phone is almost pointless since you'll get a new phone in three or four years however adding a Z at the start of their contact means when you import your contacts to the new phone and a bad contact calls you then you know not to pick up.