Details
- 
    Bug 
- 
    Status: Closed (View Workflow)
- 
    Critical 
- 
    Resolution: Fixed
- 
    N/A
- 
    None
Description
serg wrote elsewhere:
Conditions under which online alter works are getting more and more complicated, lots of cases will disable online mode. Perhaps it'd make sense to issue a warning of why exactly online was disabled? Otherwise, I suspect, users will be hardly able to navigate this maze of conditions.
So far this extra diagnostics has not been implemented, error messages still look the way they did before:
| bb-11.0-oalter fd06124e66c | 
| MariaDB [test]> alter online table t1 rename to t1a; | 
| ERROR 1845 (0A000): LOCK=NONE/SHARED is not supported for this operation. Try LOCK=EXCLUSIVE | 
| MariaDB [test]> show warnings; | 
| +-------+------+--------------------------------------------------------------------------+ | 
| | Level | Code | Message | | 
| +-------+------+--------------------------------------------------------------------------+ | 
| | Error | 1845 | LOCK=NONE/SHARED is not supported for this operation. Try LOCK=EXCLUSIVE | | 
| +-------+------+--------------------------------------------------------------------------+ | 
| 1 row in set (0.000 sec) | 
Attachments
Issue Links
- is caused by
- 
                    MDEV-16329 Engine-independent online ALTER TABLE -         
- Closed
 
-         
- relates to
- 
                    MDEV-30906 Variable alter_algorithm=COPY takes precedence over explicit ALGORITHM clause -         
- Stalled
 
-         
- 
                     MDEV-28808
        Test MDEV-16329 (ALTER ONLINE TABLE) - Core server part MDEV-28808
        Test MDEV-16329 (ALTER ONLINE TABLE) - Core server part-         
- Closed
 
-