Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
13.1
-
None
-
Not for Release Notes
-
Q3/2026 Server Development
Description
https://buildbot.mariadb.org/#/builders/639/builds/26544
Below is the failure in "test-nm". Could be simply the test introduced in MDEV-40467 (part of MDEV-15621) uses 64bit endtime Y2106 whereas 32bit endtime is Y2038, in which case should be a quick and easy fix
main.partition_range_interval w8 [ fail ]
|
Test ended at 2026-08-05 13:48:23
|
|
|
CURRENT_TEST: main.partition_range_interval
|
mysqltest: At line 1053: query 'create table t1 (c timestamp) engine=innodb
|
PARTITION BY RANGE COLUMNS (c)
|
INTERVAL 1 day
|
(
|
PARTITION p0 VALUES LESS THAN ('2106-02-01')
|
)' failed: ER_WRONG_TYPE_COLUMN_VALUE_ERROR (1654): Partition column values of incorrect type
|
|
|
The result from queries just before the failure was:
|
< snip >
|
PARTITION BY RANGE COLUMNS (c)
|
INTERVAL "hello" DAY
|
(
|
PARTITION p0 VALUES LESS THAN ('2026-04-20')
|
);
|
ERROR HY000: Wrong parameters for partitioned `t1`: wrong value for 'INTERVAL'
|
#
|
# MDEV-40467 Auto-partition fails when using maximum timestamp
|
#
|
SET time_zone='+00:00';
|
set timestamp=4294967295;
|
Warnings:
|
Warning 1292 Truncated incorrect timestamp value: '4294967295'
|
## out of range with TIMESTAMP
|
create table t1 (c timestamp) engine=innodb
|
PARTITION BY RANGE COLUMNS (c)
|
INTERVAL 1 day
|
(
|
PARTITION p0 VALUES LESS THAN ('2106-02-01')
|
);
|
Attachments
Issue Links
- is caused by
-
MDEV-15621 Implement interval partitioning similar to Oracle
-
- Closed
-
