Bug #106738 Incorrect documentation of global connection memory cap and counting

• Submitted: 15 Mar 2022 13:02
• Modified: 16 Mar 2022 19:55
• Reporter: Norvald Ryeng
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 8.0.28
• OS: Any
• Assigned to: Jon Stephens
• CPU Architecture: Any

[15 Mar 2022 13:02] Norvald Ryeng

Description:
The manual incorrectly states that memory allocated by system threads or super users is not included in the global connection memory count:

https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_global_connect...
https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Global_connec...

The memory used by these threads/connections is actually counted, but system threads and super user connections are never aborted/disconnected because of memory usage. I.e., the memory usage is counted, and even if these threads aren't aborted, other threads can be aborted because these threads bring the total (global) connection memory count beyond the global_connection_memory_limit.

This feature was introduced in 8.0.28. Older versions are not affected by this doc bug.

How to repeat:
N/A

Suggested fix:
Document that the _limits_ don't apply to these threads, but that the memory they allocate is counted.

[15 Mar 2022 21:13] Jon Stephens

This one should be mine.

[16 Mar 2022 19:55] Jon Stephens

Fixed in mysqldoc r72312, mysql-relnotes r24353.

Closed.