[MDEV-33358] ROW END needs to be adjusted to 32-bit timestamp upon OM => NS replication Created: 2024-02-01 Updated: 2024-02-01 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Replication, Temporal Types, Versioned Tables |
| Affects Version/s: | N/A |
| Fix Version/s: | 11.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Michael Widenius |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Monty was going to fix it anyway, but since it hasn't happened yet, I'll file it so it's not forgotten. I don't think it is an absolute show-stopper for RC, but it must be fixed before GA (of whatever version the feature goes into). Upon RBR from an old master to a server with 32-bit timestamp ROW END values of system-versioned tables are written in the binary log explicitly and are replicated "as is" (2038-...), so they become historical rows on the new server. It is true both for tables with automatic ROW START/END fields and for custom ones, when versioning is timestamp-based. On an old master:
The binary log:
On the new server:
|