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

Introduce SET GLOBAL innodb_max_purge_lag_wait

    XMLWordPrintable

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/755

      gcol.innodb_virtual_debug_purge 'innodb' w3 [ fail ]
              Test ended at 2018-08-10 21:48:13
       
      CURRENT_TEST: gcol.innodb_virtual_debug_purge
      --- /usr/share/mysql-test/suite/gcol/r/innodb_virtual_debug_purge.result	2018-08-10 19:08:32.000000000 +0000
      +++ /dev/shm/var/3/log/innodb_virtual_debug_purge.reject	2018-08-10 21:48:13.389484458 +0000
      @@ -200,7 +200,7 @@
       disconnect prevent_purge;
       connection default;
       SET DEBUG_SYNC='now WAIT_FOR purge_start';
      -InnoDB		1 transactions not purged
      +InnoDB		2 transactions not purged
       SET DEBUG_SYNC='now SIGNAL release';
       SET GLOBAL debug_dbug=@old_dbug;
       connection truncate;
       
      mysqltest: Result content mismatch
       
       - skipping '/dev/shm/var/3/log/gcol.innodb_virtual_debug_purge-innodb/'
       
      Retrying test gcol.innodb_virtual_debug_purge, attempt(2/3)...
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: