diff options
author | Vladislav Vaintroub <wlad@mariadb.com> | 2018-04-11 23:07:23 +0100 |
---|---|---|
committer | Vladislav Vaintroub <wlad@mariadb.com> | 2018-04-12 11:15:27 +0100 |
commit | 15071226a04125976e19a552103821eeb7227d75 (patch) | |
tree | 13ae44d66f5e43d76f122e6df996e0c6d488342e /mysql-test/suite/mariabackup/absolute_ibdata_paths.result | |
parent | 0ae13b51d780d4c0e2ef6fc251a8e03140663d35 (diff) | |
download | mariadb-git-15071226a04125976e19a552103821eeb7227d75.tar.gz |
MDEV-15780 : Mariabackup with absolute paths in innodb_data_file_path
System tablespace can be specified with absolute path, if innodb_data_home_dir
is empty.
This was not handled well by mariabackup
1. In backup phase, empty innodb_data_home_dir variable from server was
not recognized. full paths were stored in backup-my.ini, even if
it stored all files locally. thus prepare phase would not find the system
tablespace files.
2. In copy-back phase, copy would not be done to the absolute destination
path, as path would be stripped with trim_dotslash
This patch fixes the above defects.
Diffstat (limited to 'mysql-test/suite/mariabackup/absolute_ibdata_paths.result')
-rw-r--r-- | mysql-test/suite/mariabackup/absolute_ibdata_paths.result | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/mysql-test/suite/mariabackup/absolute_ibdata_paths.result b/mysql-test/suite/mariabackup/absolute_ibdata_paths.result new file mode 100644 index 00000000000..fe211e71f2f --- /dev/null +++ b/mysql-test/suite/mariabackup/absolute_ibdata_paths.result @@ -0,0 +1,10 @@ +CREATE TABLE t(i INT) ENGINE INNODB; +INSERT INTO t VALUES(1); +# xtrabackup backup +# remove datadir +# xtrabackup copy back +# restart server +SELECT * from t; +i +1 +DROP TABLE t; |