10.1 testing (MDEV-6958)

[MDEV-6963] Testing for max_query_time Created: 2013-01-04  Updated: 2021-05-27  Resolved: 2021-05-27

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1.1
Fix Version/s: N/A

Type: Technical task Priority: Minor
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-4007 max_query_timeout is not shown upon S... Open
relates to MDEV-4008 Wrong explanation of max_query_time i... Closed
relates to MDEV-4427 query timeouts Closed

 Description   

Development task: MDEV-4427
Git commit: https://github.com/MariaDB/server/commit/cc8aed3

KB: https://kb.askmonty.org/en/how-to-limittimeout-queries/#max_query_time-variable

Server option: max-statement-time
System variable: max_statement_time (global, session)
Status variable: max_statement_time_exceeded

Field in mysql.user: max_statement_time

GRANT syntax:

GRANT USAGE ON *.* TO user1@localhost WITH MAX_STATEMENT_TIME 1.005;

Related bugs:
http://bugs.mysql.com/bug.php?id=64556 (supposed to be fixed in maria-5.5-monty revno 3612 (of Jan 04))
http://bugs.mysql.com/bug.php?id=60682

 Comments   
Comment by Elena Stepanova [ 2021-05-27 ]

max_statement_time is used extensively in tests.

Generated at Thu Feb 08 07:15:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.