[MDEV-8235] Expose functionality of check_slave_start_position Created: 2015-05-26  Updated: 2015-10-31

Status: Open
Project: MariaDB Server
Component/s: Replication
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Rhys Campbell Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

The following c file...

https://github.com/MariaDB/server/blob/d4e3aa4c6f4fb467b7f1adacd8ea9f71339cffe0/sql/sql_repl.cc

Contains a function called check_slave_start_position. It would be useful to expose this, perhaps as a SQL function, in order to see if failover will function, at least from a GTID perspective.

i.e.

SELECT CHECK_SLAVE_START_POS('1-1-55');

  1. Returns true if binlog contains gtid, otherwise false

 Comments   
Comment by Sergei Golubchik [ 2015-05-28 ]

knielsen, what do you think about it?

Comment by Kristian Nielsen [ 2015-05-28 ]

> what do you think about it?

I think such discussions belong on the mailing list, not in random jira comment ...

Comment by Kristian Nielsen [ 2015-05-28 ]

Wrt. the suggestion. check_slave_start_position() is an internal
function. It does not seem too useful to expose as SQL to me. Its semantics
is quite complicated.

Maybe someone else would find it useful. It would require properly
documenting what exactly its semantics is. It is not something I plan to
work on...

Comment by Rhys Campbell [ 2015-05-28 ]

@Kristian It's wrong to create a feature requests for a feature request?

Shame. I think a lot of DBAs would like this. MySQL has a sort of similar ability....

https://www.percona.com/blog/2014/05/19/errant-transactions-major-hurdle-for-gtid-based-failover-in-mysql-5-6/

Thanks anyway.

Generated at Thu Feb 08 07:25:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.