Skip to content

Less aggressive multiplexing #394

Closed
Closed
@renecannao

Description

@renecannao

Why

Currently ProxySQL is very aggressive with multiplexing: any connection that doesn't have an active transaction can be used by other clients. This is a too aggressive multiplexing

What

Disable multiplexing for (temporary list) :

  • session variable
  • CREATE TEMPORARY TABLE
  • LOCK TABLES (and re-enable with UNLOCK TABLES)
  • GET_LOCK

The check for these criteria is done only if:

  • mysql-query_digests is enabled
  • the statement was successful : if the statements failed, we assume none of the criteria can be meet. For example, CREATE TEMPORARY TABLE failed

Do not close this issue without first documenting this feature

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions