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

wrong table name in innodb's "row too big" errors

Details

    Description

      Error log contains

      2023-09-07 23:01:37 4 [ERROR] InnoDB: Cannot add field `f32` in table `mysqld.1`.`#sql-temptable-60cc-4-f` because after adding it, the row size is 8187 which is greater than maximum allowed size (8126 bytes) for a record on index leaf page.

      instead of

      2023-09-07 23:01:37 4 [ERROR] InnoDB: Cannot add field `f32` in table `test`.`t1` because after adding it, the row size is 8187 which is greater than maximum allowed size (8126 bytes) for a record on index leaf page.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          serg Sergei Golubchik created issue -
          serg Sergei Golubchik made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          serg Sergei Golubchik made changes -
          Status In Progress [ 3 ] Stalled [ 10000 ]
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ] Marko Mäkelä [ marko ]
          Status Stalled [ 10000 ] In Review [ 10002 ]
          marko Marko Mäkelä added a comment -

          Looks good to me. However, if MDEV-22168 is implemented, it would be nice to be able to identify the partition. Partition names are part of the InnoDB table name, but not the SQL layer table name.

          marko Marko Mäkelä added a comment - Looks good to me. However, if MDEV-22168 is implemented, it would be nice to be able to identify the partition. Partition names are part of the InnoDB table name, but not the SQL layer table name.
          marko Marko Mäkelä made changes -
          Assignee Marko Mäkelä [ marko ] Sergei Golubchik [ serg ]
          Status In Review [ 10002 ] Stalled [ 10000 ]
          serg Sergei Golubchik added a comment - - edited

          Partition names don't matter in this context as all partitions have the same table structure. That is when any partition violates the InnoDB restriction the whole table needs to be created differently.

          Actually, no. If one can create different partitions using different InnoDB page size, then, indeed, the error might apply only to a specific partition, and then the partition name would be meaningful to know too

          serg Sergei Golubchik added a comment - - edited Partition names don't matter in this context as all partitions have the same table structure. That is when any partition violates the InnoDB restriction the whole table needs to be created differently. Actually, no. If one can create different partitions using different InnoDB page size, then, indeed, the error might apply only to a specific partition, and then the partition name would be meaningful to know too
          serg Sergei Golubchik made changes -
          Fix Version/s 10.4.32 [ 29300 ]
          Fix Version/s 10.5.23 [ 29012 ]
          Fix Version/s 10.6.16 [ 29014 ]
          Fix Version/s 10.10.7 [ 29018 ]
          Fix Version/s 10.11.6 [ 29020 ]
          Fix Version/s 11.0.4 [ 29021 ]
          Fix Version/s 11.1.3 [ 29023 ]
          Fix Version/s 10.4 [ 22408 ]
          Fix Version/s 10.5 [ 23123 ]
          Fix Version/s 10.6 [ 24028 ]
          Fix Version/s 10.10 [ 27530 ]
          Fix Version/s 10.11 [ 27614 ]
          Fix Version/s 11.0 [ 28320 ]
          Fix Version/s 11.1 [ 28549 ]
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          monty Michael Widenius added a comment -

          InnoDB page size cannot be changed after MariaDB bootstrap. All partitions has the same page size.

          monty Michael Widenius added a comment - InnoDB page size cannot be changed after MariaDB bootstrap. All partitions has the same page size.
          mariadb-jira-automation Jira Automation (IT) made changes -
          Zendesk Related Tickets 202463

          People

            serg Sergei Golubchik
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.