diff options
| author | Leonard Zhou <leonard@mysql.com> | 2009-03-24 08:45:05 +0800 |
|---|---|---|
| committer | Leonard Zhou <leonard@mysql.com> | 2009-03-24 08:45:05 +0800 |
| commit | 5fdc5510ec1abcfe3f3f74a229ae3102533f46c4 (patch) | |
| tree | 7bf3c31bd2c0fd5a64cef0cc9dc0f3fe2aa7687d /server-tools/instance-manager/options.cc | |
| parent | b4fdb8aec14b533db4a5ea2f99c1a9f3ce07946c (diff) | |
| download | mariadb-git-5fdc5510ec1abcfe3f3f74a229ae3102533f46c4.tar.gz | |
BUG#41719 delayed INSERT into timestamp col needs set time_zone for concurrent binlogging
When do 'insert delayed' operation, the time_zone info doesn't be keeped in the row info.
So when we do insert sometime later, time_zone didn't write into binlog.
This will cause wrong result for timestamp column in slave.
Our solution is that adding time_zone info with the delayed-row and
restoring time_zone from row-info when execute that row in the furture by another thread.
So we can write correct time_zone info into binlog and got correct result in slave.
mysql-test/r/rpl_timezone.result:
Test result
mysql-test/t/rpl_timezone.test:
Add test for bug#41719
sql/sql_insert.cc:
Add time_zone info in the delayed-row and restore time_zone when execute the row in the furture by another thread.
Diffstat (limited to 'server-tools/instance-manager/options.cc')
0 files changed, 0 insertions, 0 deletions