Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-3632

LP:695304 - Incorrect value reported for optimizer_switch by maria-5.3-wl21

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      When constructing and reporting the current value of optimizer_switch , maria-5.3-wl21 does not put a comma between index_merge_sort_union and index_condition_pushdown. This prevents the value from being parsed properly

      To repeat:

      sql/mysqld --verbose --help | grep optimizer_switch

      optimizer_switch index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=offindex_condition_pushdown=on,firstmatch=on,loosescan=on,materialization=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr_sort_keys=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,table_elimination=on

      Note the string contains "index_merge_sort_intersection=offindex_condition_pushdown=on" with no comma.

      If the variable is accessed via SELECT @@optimizer_switch or via information_schema, the correct value is reported

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            ratzpo Rasmus Johansson added a comment -

            Launchpad bug id: 695304

            Show
            ratzpo Rasmus Johansson added a comment - Launchpad bug id: 695304

              People

              • Assignee:
                igor Igor Babaev
                Reporter:
                philipstoev Philip Stoev
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: