Change Is Inevitable
  • Home
  • MySQL
    • MySQL-Articles
    • AWS RDS
    • Percona Xtradb Cluster
    • MariaDB
    • Galera Cluster
    • ProxySQL
    • MySQL-Scripts
    • MySQL tools
    • MySQL Resources
  • Tools
    • MySQL Advisor
    • MySQL Random Data Generator
    • Postgresql Random Data Generator
    • Clean Prompt
  • General
    • binary-to-decimal
    • Fermat’s Theorem
    • Review
    • Just for fun
    • Personal
  • Contact Me
    • Copyright
    • MySQL Podcast (Youtube)
    • MySQL Podcast (Spotify)
Recent Posts
  • MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • How to setup and use Percona Binlog Server (PBS)
  • MySQL Major Version Upgrade Checklist – how to
  • InnoDB Flushing is simple – explained
  • MySQL Tools for Performance Tuning and Test Data Generation
Recent Comments
  • Kedar on MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • Jean-François Gagné on MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • Reggie on A Unique Foreign Key issue in MySQL 8.4
  • Kedar on How to fix write latency in MySQL 8.4 Upgrade
  • Kedar on How to fix write latency in MySQL 8.4 Upgrade
Home » MySQL ERROR 1731
Change Is Inevitable

Kedar Vaijanapurkar's Blog for MySQL, technology and various subjects

  • Home
  • MySQL
    • MySQL-Articles
    • AWS RDS
    • Percona Xtradb Cluster
    • MariaDB
    • Galera Cluster
    • ProxySQL
    • MySQL-Scripts
    • MySQL tools
    • MySQL Resources
  • Tools
    • MySQL Advisor
    • MySQL Random Data Generator
    • Postgresql Random Data Generator
    • Clean Prompt
  • General
    • binary-to-decimal
    • Fermat’s Theorem
    • Review
    • Just for fun
    • Personal
  • Contact Me
    • Copyright
    • MySQL Podcast (Youtube)
    • MySQL Podcast (Spotify)

Browsing Tag

MySQL ERROR 1731

1 post
ALGORITHM=INSTANT Exchange Partition
  • MySQL
  • MySQL-Articles
  • 2 comments

MySQL INSTANT DDL breaks EXCHANGE PARTITION

  • Kedar
  • September 14, 2026
MySQL ERROR 1731 ‘Non matching attribute INSTANT COLUMN(s)’ breaks EXCHANGE PARTITION after ALGORITHM=INSTANT. This blog offers reasoning and fixtures.
View Post
MySQL Podcast (Youtube)
RSS feed: MySQL Podcast (Spotify) MySQL Podcast (Spotify)
  • MySQL Major Version Upgrade Checklist (Zero Downtime Strategy)
    Upgrading MySQL major versions in production is never just a version bump - it’s a carefully planned process involving compatibility checks, replication strategy, testing, and controlled cut-over.In this episode, we walk through a practical MySQL Major Version Upgrade Checklist based on real-world DBA workflows. We are covering MySQL replication as base setup for upgrade. It […]
Search:
... ...
  • MySQL INSTANT DDL breaks EXCHANGE PARTITION
  • How to setup and use Percona Binlog Server (PBS)
  • MySQL Major Version Upgrade Checklist – how to
  • InnoDB Flushing is simple – explained
  • MySQL Tools for Performance Tuning and Test Data Generation

2 responses to “MySQL INSTANT DDL breaks EXCHANGE PARTITION”

  1. Jean-François Gagné Avatar
    Jean-François Gagné
    September 14, 2026

    I had a blog post in draft on the same subject, so I am glad you published this, as I do not know when I would have gotten around to finishing mine.

    You might not have seen the verified documentation bug that I opened on this issue: https://bugs.mysql.com/bug.php?id=120016.

    I should have mentioned the documentation bug in Bug #104970 when I originally opened it. I have now updated the bug report to include that reference.

    Also note that in the verified Bug #95484 (https://bugs.mysql.com/bug.php?id=95484), I show that it is possible to have different partition formats within the same partitioned table, so I think that, with a little work, EXCHANGE PARTITION could be made to work for tables affected by INSTANT DDL.

    Reply
    1. Kedar Avatar
      Kedar
      September 17, 2026

      Thank for sharing additional information JFG, as always. Those bug reports are good read.
      About the bug https://bugs.mysql.com/bug.php?id=95484 for ROW_FORMAT and EXCHANGE PARTITION, AFAIK it failed even after having same row-format is because the logic checks “atleast 1 partition with diff”.
      Regards,
      Kedar

      Reply
Change Is Inevitable
Designed & Developed by Code Supply Co.