mirror of
https://github.com/MariaDB/server.git
synced 2025-07-27 18:02:13 +03:00
increase performance-schema-max-thread-instances
the value of 200 isn't enough for some tests anymore, this causes some random threads to become not instrumented and any table operations there are not reflected in the perfschema. If, say, a DROP TABLE doesn't change perfschema state, perfschema tables might show ghost tables that no longer exist in the server
This commit is contained in:
@ -92,7 +92,7 @@ loose-performance-schema-events-statements-history-size=10
|
||||
loose-performance-schema-events-statements-history-long-size=1000
|
||||
loose-performance-schema-events-transactions-history-size=10
|
||||
loose-performance-schema-events-transactions-history-long-size=1000
|
||||
loose-performance-schema-max-thread-instances=200
|
||||
loose-performance-schema-max-thread-instances=400
|
||||
loose-performance-schema-session-connect-attrs-size=2048
|
||||
loose-performance-schema-max-metadata-locks=10000
|
||||
|
||||
|
Reference in New Issue
Block a user