Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
Currently timestamp is 32-bit signed, although negative values are rejected, so it is de facto 31-bit, allowing values from 1970 to 2038.
We can make it 32-bit unsigned extending timestamp range to 2106, and it won't require many changes to the storage.
Storage of timestamp is not affected but the change.
However storage of 'row_end' for system versioned tables must change from storing a 2038 based timestamp to a 2106 based one.
Attachments
Issue Links
- causes
-
MDEV-32930 mysqlbinlog --verbose shows incorrect values for timestamps >= 2^31 if binlog was created with mysql56_temporal_format=off
-
- Open
-
-
MDEV-33013 versioning.insert2 fails on 32-bit with wrong result
-
- Closed
-
-
MDEV-33017 Assertion `temp > 1969' fails in Field_timestamp::val_str on 32-bit
-
- Closed
-
-
MDEV-33032 Live and dump upgrade from previous versions to the extended timestamp fails for system-versioned tables
-
- Closed
-
-
MDEV-33239 mysqlbinlog cannot parse events written with system timestamp 4294967295
-
- Closed
-
-
MDEV-33248 Connect engine does not support 32-bit timestamp
-
- Closed
-
-
MDEV-33302 Columnstore does not support 32-bit timestamps: CAL0001: MCS-2025: Data truncated for column
-
- Open
-
-
MDEV-33310 mariadb-upgrade does not fix InnoDB versioned tables upon upgrade to 32-bit timestamp
-
- Closed
-
-
MDEV-33358 ROW END needs to be adjusted to 32-bit timestamp upon OM => NS replication
-
- Closed
-
-
MDEV-33718 mariadb-dump help refers to the wrong version for timestamp upgrades
-
- Closed
-
-
MDEV-34121 Extension of timestamp range can cause OM=>NS replication discrepancy and failure
-
- Open
-
- is blocked by
-
MDEV-33449 improving repair of tables
-
- Closed
-
- is duplicated by
-
MDEV-9444 MariaDB needs to be Y2038-compliant
-
- Closed
-
-
MDEV-20192 Change timestamp to 64-bit integer for number of seconds to extend its life with EPOCH defined as '1970-01-01 00:00:01 UTC'
-
- Closed
-
-
MDEV-26736 UNIX_TIMESTAMP doesn't work beyond 2038 (aka y2.038k)
-
- Closed
-
- relates to
-
MDEV-15750 preserve MYSQL_TYPE_TIMESTAMP in temporal arithmetics
-
- Stalled
-
-
MDEV-16135 Service does not start if date set beyond Y2038
-
- Closed
-
-
MDEV-32582 Events fuctionality after 2038
-
- Open
-
-
MDEV-33381 armhf: MTR failures in Spider and versioning tests
-
- Open
-
-
MDEV-33449 improving repair of tables
-
- Closed
-
-
MDEV-341 64-bit support in FROM_UNIXTIME()
-
- Open
-
-
MDEV-10018 Timestamp with time zone
-
- Open
-
-
MDEV-32496 TIMESTAMP variant to support YEAR range -4713 and +9999
-
- Open
-
-
MDEV-33442 REPAIR TABLE corrupts UUIDs
-
- Closed
-
- links to
Activity
Link | This issue blocks TODO-4253 [ TODO-4253 ] |
Link | This issue blocks TODO-4253 [ TODO-4253 ] |
Summary | make TIMESTAMP to use whole 32-bit unsigned range | make TIMESTAMP use whole 32-bit unsigned range |
Status | Open [ 1 ] | In Progress [ 3 ] |
Description |
Currently timestamp is 32-bit signed, although negative values are rejected, so it is de facto 31-bit, allowing values from 1970 to 2038.
We can make it 32-bit unsigned extending timestamp range to 2106, and it won't require many changes of the storage. |
Currently timestamp is 32-bit signed, although negative values are rejected, so it is de facto 31-bit, allowing values from 1970 to 2038.
We can make it 32-bit unsigned extending timestamp range to 2106, and it won't require many changes to the storage. |
Description |
Currently timestamp is 32-bit signed, although negative values are rejected, so it is de facto 31-bit, allowing values from 1970 to 2038.
We can make it 32-bit unsigned extending timestamp range to 2106, and it won't require many changes to the storage. |
Currently timestamp is 32-bit signed, although negative values are rejected, so it is de facto 31-bit, allowing values from 1970 to 2038.
We can make it 32-bit unsigned extending timestamp range to 2106, and it won't require many changes to the storage. Storage of timestamp is not affected but the change. However storage of 'row_end' for system versioned tables must change from storing a 2038 based timestamp to a 2106 based one. |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Fix Version/s | 11.4 [ 29301 ] | |
Fix Version/s | 11.3 [ 28565 ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Assignee | Michael Widenius [ monty ] | Alexander Barkov [ bar ] |
Link |
This issue relates to |
Link |
This issue relates to |
Priority | Major [ 3 ] | Critical [ 2 ] |
Link | This issue relates to MDEV-32496 [ MDEV-32496 ] |
Link | This issue relates to MDEV-15750 [ MDEV-15750 ] |
Link | This issue relates to MDEV-10018 [ MDEV-10018 ] |
Assignee | Alexander Barkov [ bar ] | Michael Widenius [ monty ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Link | This issue relates to MDEV-32582 [ MDEV-32582 ] |
Status | Stalled [ 10000 ] | In Testing [ 10301 ] |
Assignee | Michael Widenius [ monty ] | Elena Stepanova [ elenst ] |
Issue Type | Task [ 3 ] | New Feature [ 2 ] |
Link | This issue causes MDEV-32930 [ MDEV-32930 ] |
Link |
This issue causes |
Link |
This issue causes |
Link |
This issue causes |
Link | This issue causes TODO-4495 [ TODO-4495 ] |
Link | This issue causes TODO-4495 [ TODO-4495 ] |
Link | This issue is part of TODO-4495 [ TODO-4495 ] |
Labels | Preview_11.4 |
Link |
This issue causes |
Link |
This issue causes |
Link | This issue causes MDEV-33302 [ MDEV-33302 ] |
Link |
This issue causes |
Link |
This issue causes |
Remote Link | This issue links to "Debian libmariadbd19t64 library name update for libc toolchain transition (Web Link)" [ 36501 ] |
Link | This issue relates to MDEV-33381 [ MDEV-33381 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Assignee | Elena Stepanova [ elenst ] | Sergei Golubchik [ serg ] |
Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
Fix Version/s | 11.5 [ 29506 ] | |
Fix Version/s | 11.4 [ 29301 ] |
Status | Stalled [ 10000 ] | In Testing [ 10301 ] |
Assignee | Sergei Golubchik [ serg ] | Elena Stepanova [ elenst ] |
Link |
This issue is blocked by |
Link | This issue is part of TODO-4630 [ TODO-4630 ] |
Link |
This issue causes |
Labels | Preview_11.4 | Preview_11.4 Preview_11.5 |
Link | This issue causes MDEV-34121 [ MDEV-34121 ] |
Assignee | Elena Stepanova [ elenst ] | Sergei Golubchik [ serg ] |
Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
Fix Version/s | 11.5.1 [ 29634 ] | |
Fix Version/s | 11.5 [ 29506 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link | This issue blocks MENT-2096 [ MENT-2096 ] |
Zendesk Related Tickets | 112719 124111 |
Link |
This issue relates to |