Some tools use @@hostname without /*!50038*/
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Low
|
Daniel Nichter | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.1 |
Fix Released
|
Low
|
Daniel Nichter | ||
2.2 |
Fix Released
|
Low
|
Daniel Nichter |
Bug Description
We do use the following mysql-server version :
Server version: 5.0.32-
When trying to run pt-table-checksum the following error arise :
03-06T12:10:03 DBD::mysql::db selectrow_array failed: Unknown system variable 'hostname' [for Statement "SELECT @@hostname, @@server_id"] at /usr/bin/
Looking at the code, it's obvious that @@hostname must be defined to succeed :
my $sql = 'SELECT @@hostname, @@server_id';
PTDEBUG && _d($dbh, $sql);
my ($hostname, $server_id) = $dbh->selectrow
PTDEBUG && _d($dbh, 'hostname:', $hostname, $server_id);
if ( $hostname ) {
$
}
You can see here that this was added in version 5.0.38 : http://
Can you add a way to override this hostname check ? maybe passing it through a command line switch.
cheers
fred
--- infos ---
command line : pt-table-checksum h=my-master-
version : pt-table-checksum 2.0.3
mysql-server-
Related branches
- Daniel Nichter: Approve
-
Diff: 127 lines (+16/-16)8 files modifiedbin/pt-config-diff (+2/-2)
bin/pt-deadlock-logger (+2/-2)
bin/pt-fk-error-logger (+2/-2)
bin/pt-kill (+2/-2)
bin/pt-online-schema-change (+2/-2)
bin/pt-table-checksum (+2/-2)
bin/pt-upgrade (+2/-2)
lib/Cxn.pm (+2/-2)
- Daniel Nichter: Approve
-
Diff: 79 lines (+10/-10)5 files modifiedbin/pt-config-diff (+2/-2)
bin/pt-kill (+2/-2)
bin/pt-online-schema-change (+2/-2)
bin/pt-table-checksum (+2/-2)
lib/Cxn.pm (+2/-2)
summary: |
- pt-table-checksum use @@hostname system variable which is not defined in - all mysql versions + Tools use @@hostname without /*!50038*/ |
tags: | added: all-tools connection |
summary: |
- Tools use @@hostname without /*!50038*/ + Some tools use @@hostname without /*!50038*/ |
We can think of a way to work around this. But, frankly, most people should not be running such an old version of 5.0 anymore. It is horribly buggy and has severe performance problems. I haven't seen any 5.0 servers older than 5.0.51a in a couple of years and it's certainly not a popular version to use. So, this is relatively low priority for us (unless you have a support contract which entitles you to a fix).