Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.10
-
None
-
None
-
RHEL 6.5 - x64
Description
I have a database table with a huge amount of partitions with a very verbose partition creation statement. It is 260K in size. I can create the tables without a problem, but am unable to open the tables once created. It appears that sql/unireg.h has FRM_MAX_SIZE defined at 256K, and silently truncates the form file to that size. open_table_def() contains this statement:
Attachments
Issue Links
- relates to
-
MDEV-15925 FRM_MAX_SIZE too low for some use cases
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | mdev6224.test [ 29601 ] | |
Assignee | Sergei Golubchik [ serg ] |
Fix Version/s | 10.0.12 [ 15201 ] |
Workflow | defaullt [ 40404 ] | MariaDB v2 [ 42538 ] |
Fix Version/s | 10.0.13 [ 16000 ] | |
Fix Version/s | 10.0.12 [ 15201 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 10.0.13 [ 16300 ] | |
Fix Version/s | 10.0 [ 16000 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v2 [ 42538 ] | MariaDB v3 [ 64030 ] |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 64030 ] | MariaDB v4 [ 147878 ] |
open_table_def() contains this statement: set_if_smaller(frmlen, FRM_MAX_SIZE); // safety
It would be helpful to at least include a warning in the error file to let me know why the load was failing. In this case, the binary loader was unable to read the names of the fields.