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

Absent progress report for operations on InnoDB tables

    Details

    • Sprint:
      10.0.20

      Description

      See also MDEV-8178

      Initially mentioned on the mailing list: https://lists.launchpad.net/maria-discuss/msg02496.html

      Dataset: salaries table in the employees sample database.

      Examples of statements that show progress report on 5.5 and 10.1, but not on 10.0.

      ALTER TABLE salaries ENGINE = Innodb;
      ALTER TABLE salaries ADD id INT NULL;
      ALTER TABLE salaries DROP id;
      ALTER TABLE salaries ROW_FORMAT = COMPRESSED;
      

      It happened somewhere between 10.0.10 and 10.0.11.

      For MyISAM, progress is displayed.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              jplindst Jan Lindström added a comment -

              In 5.5 you can see:

              MariaDB [employees]> ALTER TABLE salaries ENGINE = Innodb;
              --------------
              ALTER TABLE salaries ENGINE = Innodb
              --------------
              
              Stage: 1 of 2 'copy to tmp table'  0.808% of stage done
              

              On 10.0, there is no stage output at all.

              Show
              jplindst Jan Lindström added a comment - In 5.5 you can see: MariaDB [employees]> ALTER TABLE salaries ENGINE = Innodb; -------------- ALTER TABLE salaries ENGINE = Innodb -------------- Stage: 1 of 2 'copy to tmp table' 0.808% of stage done On 10.0, there is no stage output at all.
              Hide
              jplindst Jan Lindström added a comment -

              There is regression between 10.0.10 and 10.0.11. In 10.0.10 ALTER TABLE salaries ENGINE = Innodb; client (e.g. mysql) does print stage output but on 10.0.11 client does not print any stage outputs. Rest of above statements do not print any stage outputs on 10.0.10. In 5.5 they do because 5.5 does not include on-line alter table. In 10.1 stage outputs are printed because MDEV-6172, commit 8984bef2e431db42761d3f267b950293cfd864de introduced a new feature where InnoDB/XtraDB sends a progress messages.

              Show
              jplindst Jan Lindström added a comment - There is regression between 10.0.10 and 10.0.11. In 10.0.10 ALTER TABLE salaries ENGINE = Innodb; client (e.g. mysql) does print stage output but on 10.0.11 client does not print any stage outputs. Rest of above statements do not print any stage outputs on 10.0.10. In 5.5 they do because 5.5 does not include on-line alter table. In 10.1 stage outputs are printed because MDEV-6172 , commit 8984bef2e431db42761d3f267b950293cfd864de introduced a new feature where InnoDB/XtraDB sends a progress messages.
              Hide
              jplindst Jan Lindström added a comment -

              I'l take this back. BUG# 13975227: ONLINE OPTIMIZE TABLE FOR INNODB TABLES, so we really should use online alter table also for alter table t1 engine=innodb. I will reconsider to merge progress info from 10.1 to 10.0.

              Show
              jplindst Jan Lindström added a comment - I'l take this back. BUG# 13975227: ONLINE OPTIMIZE TABLE FOR INNODB TABLES, so we really should use online alter table also for alter table t1 engine=innodb. I will reconsider to merge progress info from 10.1 to 10.0.

                People

                • Assignee:
                  jplindst Jan Lindström
                  Reporter:
                  elenst Elena Stepanova
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Agile