Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
Debian Unstable, Debian Testing and Debian Stable
Description
Hi there,
MariaDB 10.1 doesn't support `innodb_default_row_format` yet. Since InnoDB in Debian uses `utf8mb4` as default character set since version `10.0.20-2`, this leads to major pain, e.g. due to keys longer than 767 bytes.
A lot of applications silently expect the supported maximum size of VARCHAR to be 255 characters which means 1016 bytes with `utf8mb4`.
In order to support larger keys, `innodb_large_prefix` needs to be enabled and ROW_FORMAT set to `dynamic`. The former can be configured in the MariaDB server configuration in a persistent way, the latter not due to missing configuration option `innodb_default_row_format`.
Backporting `innodb_default_row_format` will at least give the option to server admins to configure MariaDB 10.1 in a way that applications don't break if they want to create keys > 767 bytes.
PS: I already discussed this issue with Marko Mäkelä (dr-m) on IRC.
Attachments
Issue Links
- relates to
-
-
- Open
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Marko Mäkelä [ marko ] |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Fix Version/s | 10.1 [ 16100 ] |
| Component/s | Storage Engine - InnoDB [ 10129 ] | |
| Component/s | Storage Engine - XtraDB [ 10135 ] |
| Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
| Assignee | Marko Mäkelä [ marko ] | Thirunarayanan B [ thiru ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Assignee | Thirunarayanan B [ thiru ] | Marko Mäkelä [ marko ] |
| issue.field.resolutiondate | 2018-03-07 15:58:34.0 | 2018-03-07 15:58:34.291 |
| Fix Version/s | 10.1.32 [ 22908 ] | |
| Fix Version/s | 10.1 [ 16100 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10002 ] | Closed [ 6 ] |
| Link | This issue relates to MDEV-17160 [ MDEV-17160 ] |
| Workflow | MariaDB v3 [ 84805 ] | MariaDB v4 [ 153533 ] |