You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This probably also affects mysql 5.6 when gtids are used. On MariaDB when --master-data is used, a new section is included:
--
-- GTID to start replication from
--
-- SET GLOBAL gtid_slave_pos='0-1-36509';
This confuses sieve's naive tokenizer / parser which aborts on a silly error like:
# ./dbsake sieve < all_databases.sql.gz > /dev/null
Unable to determine section type at line 25: -- GTID to start replication from
Ultimately the tokenizer needs to be made more robust - similar to issue #69 where this causes issues with compact or other "non-standard" mysqldump formats.
The text was updated successfully, but these errors were encountered:
This changes the directory format to append the MariaDB GTID
section to replication_info.sql[.ext] and otherwise is just
pass through for the stream writer.
Resolves issue #78
This probably also affects mysql 5.6 when gtids are used. On MariaDB when --master-data is used, a new section is included:
This confuses sieve's naive tokenizer / parser which aborts on a silly error like:
Ultimately the tokenizer needs to be made more robust - similar to issue #69 where this causes issues with compact or other "non-standard" mysqldump formats.
The text was updated successfully, but these errors were encountered: