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

binlog_do_db option breaks importing sql dumps

Details

    Description

      If you have binlog enabled and binlog_do_db set to some table and then make a mariadb-dump and import the dump to some database different of the one set in binlog_do_db, then all the Innodb tables in that database have no records.

      I'm attaching a bash script to demonstrate the problem.
      The result from all counts should e 1, but when binlog_do_db is set the result for the innodb table changes.

      That behaviour wasn't observed in 10.5 versions. It appeared after upgrade to 10.8.
      Cannot report for the versions in between, unfortunately.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Sergei Golubchik made transition -
            Open Closed
            9d 3h 33m 1
            Sergei Golubchik made transition -
            Closed Stalled
            28m 1s 1
            Sergei Golubchik made transition -
            Stalled Open
            8s 1
            Sergei Golubchik made transition -
            Open Confirmed
            18s 1
            Thirunarayanan Balathandayuthapani made transition -
            Confirmed In Progress
            305d 19h 49m 1
            Thirunarayanan Balathandayuthapani made transition -
            In Progress In Review
            16h 32m 1
            Thirunarayanan Balathandayuthapani made transition -
            In Review Closed
            4d 22h 18m 1

            People

              thiru Thirunarayanan Balathandayuthapani
              lukav Anton Avramov
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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