Hi Sergei,

It seems limited to the salaries table in the employees sample database.

ALTER TABLE salaries ENGINE = Innodb; <- Exhibits the incorrect behaviour.

CREATE INDEX tt ON salaries (emp_no); <- Does not exhibit the behaviour.

DROP INDEX tt ON salaries; <- Does not exhibit the behaviour

ALTER TABLE salaries ADD id INT NULL; <- Exhibits the incorrect behaviour.

ALTER TABLE salaries DROP id; <- Exhibits the incorrect behaviour.

ALTER TABLE salaries ROW_FORMAT = COMPRESSED; <- Exhibits the incorrect behaviour.

Most of the tables have an estimated number of stages of 9/12/16/20 etc. The salaries table ranges from 76-84 depending on the action. Often, halfway through, the number of steps will drop down to 22.

Cheers,

Rhys

-----Original Message-----
From: Sergei Golubchik [mailto:serg@mariadb.org]
Sent: 16 May 2015 09:54
To: Rhys Campbell
Cc: maria-discuss@lists.launchpad.net
Subject: Re: [Maria-discuss] MariaDB 10.1.4 Progress output

Hi, Rhys!

On Apr 20, Rhys Campbell wrote:

> Note the progress output below. I've seen several like this. i.e...

> Stage: 1 of 72 'altering table' 350% of stage done. Is this intentional?

No, not exactly :)

This happens when the engine miscalculates number of steps it needs to do for an ALTER. If you have a test case for that behaviour, we'll fix it.

Regards,

Sergei