[MDEV-13236] Document MDEV-12179 (Per-engine mysql.gtid_slave_pos tables) Created: 2017-07-03  Updated: 2017-07-12  Resolved: 2017-07-12

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Elena Stepanova Assignee: Ian Gilfillan
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-12179 Per-engine mysql.gtid_slave_pos tables Closed

 Description   

MDEV-12179 has been pushed into 10.3 tree to be released with 10.3.1.

I see that somebody has already documented its existence of the feature and new system/status variables in the KB, but it's not enough, it needs to be documented in terms of operation, with at least minimal functional examples to show what one needs to make it work:

  • when the variable value becomes effective – after server restart, after slave restart, upon receiving certain events, etc.;
  • in which cases the extra tables are created automatically and in which they are not;
  • when user needs to create the tables manually, if ever;
  • when user needs to populate the table manually, and if so, with what;
    etc.

There is a test rpl.rpl_mdev12179, but it doesn't help, the logic appears seemingly random.

 Comments   
Comment by Kristian Nielsen [ 2017-07-11 ]

The main documentation is at https://mariadb.com/kb/en/mariadb/mysqlgtid_slave_pos-table/
I am sure it can be improved.

Comment by Ian Gilfillan [ 2017-07-12 ]

The documentation has been slightly expanded so all points should be covered. There should be no need to ever manually create a table, so this is not mentioned in the docs (except for the ALTER example).

Generated at Thu Feb 08 08:03:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.