[MDEV-16684] Wrong timestamps on restore from mysqldump --compact - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Not a Bug
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Fix Version/s: N/A
Component/s: Scripts & Clients, Time zones
Labels:
- need_feedback

Description

Reproduce

1. Set system timezone to UTC+3
2.

create or replace table d (t timestamp);

insert into d values ('2000-01-01 00:00');

mysqldump --compact test d > /tmp/dump.sql

drop table d;

source /tmp/dump.sql

select * from d;

Result

Data is different from original:

+---------------------+

| t                   |

+---------------------+

| 1999-12-31 22:00:00 |

+---------------------+

Expected

mysqldump and subsequent restore should be idempotent without any additional manipulations.

Fix

mysqldump must insert correct SET time_zone directive regardless --compact setting. In case when opt_tz_utc is 0 it must detect server timezone as well.

Attachments

Issue Links

blocks

MDEV-16029 mysqldump: dump and restore historical data

Closed

relates to

MDEV-16013 During the extra hour upon DST switch historical data from time-versioned tables is shown inconsistently

Stalled

MDEV-16752 mysqldump: racing condition in STDERR+STDOUT output

Closed

Activity

People

Assignee:: Aleksey Midenkov

Reporter:: Aleksey Midenkov

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2018-07-04 14:47

Updated:: 2021-02-28 18:35

Resolved:: 2019-09-20 00:50

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.