1. Bug MXS-5403
    Debug assertion on very large binary protocol prepared statements
  2. Bug MXS-4608
    History response checks are not always done
  3. Bug MXS-5382
    Errors due to max_connections being exceeded are always fatal errors
  4. Task MXS-3993
    Use native capability API from C/C
  5. Bug MXS-3850
    MaxScale misinterprets SET GLOBAL autocommit=0
  6. Bug MXS-1826
    COM_CHANGE_USER not work with Oracle MySQL
  7. New Feature MXS-3291
    SQL Server TDS Protocol Support
  8. Bug MXS-6017
    Adapt to MDEV-37554 protocol changes
  9. Bug MXS-5010
    Session commands that are executed early are not validated
  10. Bug MXS-5006
    maxscale crash
  11. Bug MXS-4998
    MaxScale may send two COM_QUIT packets
  12. New Feature MXS-5367
    Support zstd protocol compression
  13. New Feature MXS-5069
    support bulk returning all individual results
  14. Bug MXS-5032
    COM_STMT_PREPARE that modifies the session state is not executed on history replay
  15. Task MXS-5391
    Refactor result processing code into separate states
  16. Bug MXS-5577
    Aborted connection on backend mariadb with persistpool maxscale
  17. New Feature MXS-4635
    Provide load balancing metadata to connectors
  18. Task MXS-4644
    Wait for database users update
  19. New Feature MXS-4639
    Add support for pipelined execution of COM_STMT_PREPARE
  20. Task MXS-4532
    Postgres filter/router support
  21. Task MXS-4529
    Postgres backend protocol support
  22. Task MXS-4528
    Postgres client protocol support
  23. Bug MXS-4726
    Session command response verification unnecessarily stores PS IDs for readconnroute
  24. Task MXS-5506
    Make UserDatabase public.
  25. Bug MXS-4879
    Transaction state viewed from the session is different from the transaction state as viewed from RWS.
  26. Bug MXS-3829
    Debug asssert in 2.5
  27. Bug MXS-3801
    Unexpected internal state with read-only cursor and result with one row
  28. Bug MXS-3775
    Hang in RoutingWorker::execute_concurrently
  29. New Feature MXS-4286
    Postgres protocol support
  30. Bug MXS-4283
    Race condition in KILL command processing
  31. Bug MXS-4334
    Unknown protocol commands should be rejected
  32. Bug MXS-3436
    Packet received out-of-order. Expected 1; got 3
  33. New Feature MXS-3616
    Support MARIADB_CLIENT_EXTENDED_TYPE_INFO
  34. Bug MXS-3533
    MaxScale doesn't advertise the SESSION_TRACK capability
  35. Bug MXS-3515
    COM_STMT_EXECUTE with ID -1 isn't handled correctly
  36. Bug MXS-4141
    connection_keepalive=0 causes a memory leak
  37. Bug MXS-4101
    Unexpected result with mixed 10.2 and 10.6 backends
  38. Bug MXS-3984
    COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends
  39. Bug MXS-3940
    Debug assertion in mariadb_backend.cc
  40. New Feature MXS-5238
    Connection redirection: add redirect_url parameter
  41. Bug MXS-5143
    Proxy protocol v2 headers from AWS do not seem to work
  42. Task MXS-3362
    Make session commands a generic mechanism
  43. Task MXS-3361
    Rewrite ignorable query processing
  44. Bug MXS-3297
    Extended MariaDB capabilities are not read correctly
  45. Bug MXS-4429
    Many "Unknown prepared statement handler" warnings after upgrade to 6.4
  46. Bug MXS-4865
    5.5.5- prefix should not be added if all backends are MariaDB 11
  47. Sub-Task MXS-3375
    Make PS management a generic feature
  48. Bug MXS-2525
    before upgrade to 2.3, all works well ,after upgrade maxscale to 2.3.7，some programing drivers can not work well
  49. Bug MXS-2538
    MaxScale sends wrong charset in some cases
  50. Bug MXS-2536
    Hang on KILL /*QUERY*/ 1
Refresh results