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

Merge MDEV-37146 into MDEV-39519

    XMLWordPrintable

Details

    • Q3/2026 Replic. Maintenance

    Description

      In MDEV-37146, mariadb-dump queries information_schema.SLAVE_STATUS if the server is MariaDB 11.6+ and SHOW SLAVE STATUS otherwise.
      OTOH, in MDEV-39519, mariadb-dump always queries SHOW REPLICA STATUS first and then SHOW SLAVE STATUS if the former is not supported.

      These two conflict, not just in code, but in their approaches.

      In the mailing list, bnestere recommended to port In MDEV-37146's information_schema.SLAVE_STATUS to MDEV-39519's attempt-based approach.

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-37146 mariadb-dump: Replace SHOW SLAVE STATUS usage with information_schema.SLAVE_STATUS

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-39519 Change mariadb-dump to use SHOW REPLICA STATUS instead of SHOW SLAVE STATUS

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-40073 Merge MySQL support in mariadb-dump into 13.0

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              ParadoxV5 Jimmy Hú
              ParadoxV5 Jimmy Hú
              Brandon Nesterenko Brandon Nesterenko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.