thread_pool_high_prio_mode

Support CLI: Yes

Support configuration file: Yes

Support dynamic modification: Yes

Scope: global, session

Parameter type: string

Default value: transactions

Possible values: transactions, statements, and none

This parameter is used to provide finer-grained control over high-priority scheduling either global or per-connection.

• transactions: Only statements from started transactions can enter the high-priority queue, depending on the number of high-priority tickets currently available in the connection (see thread_pool_high_prio_tickets).
• statements: All individual statements enter the high-priority queue, regardless of the transactional status of the connection or the number of available high-priority tickets. This option can be used to prioritize sessions for specific connections. (Note that setting this value globally essentially disables high priority scheduling, since in this case all statements from all connections have the same priority.)
• none: The high-priority queue of a connection is disabled. You can use this option for connections (for example, monitoring) that are insensitive to execution latency and never occupy any server resources that would otherwise impact performance in other connections. Such connections do not really require high priority scheduling. (Note that setting this value globally essentially disables high priority scheduling.)