Bug #101217 | Thoughts on 13.4.2.10 Functions which Configure the Source List | ||
---|---|---|---|
Submitted: | 17 Oct 2020 10:08 | Modified: | 21 Oct 2020 17:52 |
Reporter: | Simon Mudd (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S4 (Feature request) |
Version: | 8.0.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Docs, multiple_sources, udf |
[17 Oct 2020 10:08]
Simon Mudd
[17 Oct 2020 11:36]
Simon Mudd
Related: https://bugs.mysql.com/bug.php?id=101218
[18 Oct 2020 5:47]
MySQL Verification Team
Hello Simon, Thank you for the reasonable feature request! regards, Umesh
[21 Oct 2020 17:38]
Kenny Gryp
Hello Simon, One of the suggestions in this bug was to provide a UDF to list the sources. It is possible to query the replication_asynchronous_connection_failover performance schema table to get the configuration https://dev.mysql.com/doc/refman/8.0/en/performance-schema-replication-asynchronous-connec... What benefit do you see in having the UDF to list the config compared to just querying the pfs table?
[21 Oct 2020 17:50]
Simon Mudd
Hi Kenny, One of the reasons to suggest the 3rd UDF is for consistency. The second is there was no mention of this table in the documentation I saw. Now I see that there's a performance_schema.replication_asynchronous_connection_failover table personally I'd be tempted to ask why you don't simply allow configuration changes to this table (via INSERT/UPDATE/DELETE) and ensure that DMLs are not replicated which has been the cases since I reported a bug in 5.6.5 where I saw this happen unintentionally. So yes, now I know the structure of the P_S table that could be used. Please ensure there's a reference to this in the section mentioned for people who need to verify the settings. Looking at the table definition of replication_asynchronous_connection_failover I see we still use utf8 rather than utf8mb4 which seems somewhat surprising.
[21 Oct 2020 17:52]
Simon Mudd
Other p_s tables are used for configuration such as the setup_* tables. Why does replication_asynchronous_connection_failover require special treatment?