Comments - System-Versioned Tables

6 years, 3 months ago shi wei hong

Hello, I want to use the System-Versioned Tables on slave.

I tested 2 MySQL versions (5.6.25,5.7.16),and the master binlog format is ROW,the slave version is 10.3.7-MariaDB.

When I insert rows into the master,the result on master is

mysql> select * from t;
+------+
| x    |
+------+
|    1 |
|    2 |
|    3 |
+------+
3 rows in set (0.00 sec).

But on slave:

MariaDB [test]> select * from t;
Empty set (0.001 sec)

MariaDB [test]> select *,row_start,row_end from t for system_time all;
+------+----------------------------+----------------------------+
| x    | row_start                  | row_end                    |
+------+----------------------------+----------------------------+
|    1 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
|    2 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
|    3 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
+------+----------------------------+----------------------------+
3 rows in set (0.000 sec).

the row_start and row_end be set to '0000-00-00 00:00:00.000000'.

When I insert rows into the slave, it work normally:

MariaDB [test]> insert into t values (4);
Query OK, 1 row affected (0.009 sec)

MariaDB [test]> select * from t;
+------+
| x    |
+------+
|    4 |
+------+
1 row in set (0.000 sec)

MariaDB [test]> select *,row_start,row_end from t for system_time all;
+------+----------------------------+----------------------------+
| x    | row_start                  | row_end                    |
+------+----------------------------+----------------------------+
|    1 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
|    2 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
|    3 | 0000-00-00 00:00:00.000000 | 0000-00-00 00:00:00.000000 |
|    4 | 2018-06-13 16:01:52.073203 | 2038-01-19 11:14:07.999999 |
+------+----------------------------+----------------------------+

What should I do to solve this problem?

Archived  
6 years, 3 months ago Sergei Golubchik

This is a bug. Could you please report it at jira.mariadb.org? We'll have it fixed in 10.3.8.

 
6 years, 3 months ago shi wei hong

OK,I had report it at jira.mariadb.org, the issues number is MDEV-16485.

 
6 years, 1 month ago Salvatore C

Was this every resolved? I don't see any movement on the ticket and the status is "stalled"

 
6 years, 1 month ago Sergei Golubchik

Yes, it was fixed in 10.3.8.

I've updated the issue status now, sorry for confusion.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.