Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2450

Crash on COM_CHANGE_USER with disable_sescmd_history=true

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.6
    • Fix Version/s: 2.3.7
    • Component/s: readwritesplit
    • Labels:
      None

      Description

      The code that discards the session command history will cause a crash if the first session command that is executed is COM_CHANGE_USER and session command history is disabled. Removing disable_sescmd_history=true and adding prune_sescmd_history=true will prevent the crash.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration