[PT-241] Slave queries doesn't run on 5.7 Created: 05/Jan/18  Updated: 13/Jun/18  Resolved: 13/Jun/18

Status: Done
Project: Percona Toolkit
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.11

Type: Bug Priority: Medium
Reporter: Marcelo Altmann Assignee: Carlos Salguero
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 1 hour
Original Estimate: Not Specified


 Description   

Slave queries are missing the full qualified database name and always return empty result:

 

slave_status() {
   local outfile=$1
   local mysql_version=$2

   if [ "${mysql_version}" '<' "5.7" ]; then
      local sql="SHOW SLAVE STATUS\G"  
      echo -e "\n$sql\n" >> $outfile
      $CMD_MYSQL $EXT_ARGV -e "$sql" >> $outfile
   else
      local sql="SELECT * FROM performance_schema.replication_connection_configuration JOIN performance_schema.replication_applier_configuration USING(channel_name)\G"
      echo -e "\n$sql\n" >> $outfile
      $CMD_MYSQL $EXT_ARGV -e "$sql" >> $outfile

      sql="SELECT * FROM replication_connection_status\G"
      echo -e "\n$sql\n" >> $outfile
      $CMD_MYSQL $EXT_ARGV -e "$sql" >> $outfile

      sql="SELECT * FROM replication_applier_status JOIN replication_applier_status_by_coordinator USING(channel_name)\G"
      echo -e "\n$sql\n" >> $outfile
      $CMD_MYSQL $EXT_ARGV -e "$sql" >> $outfile
   fi

}


 Comments   
Comment by Marcelo Altmann [ 05/Jan/18 ]

committed PR https://github.com/percona/percona-toolkit/pull/294

Generated at Wed Nov 21 01:20:35 UTC 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.