percona/percona-toolkit
1
0
Fork 0
mirror of https://github.com/percona/percona-toolkit.git synced 2025-09-06 04:17:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

PT-1194 - LP #1266896: pt-table-sync port problem

Browse Source 
- Fixed typos
This commit is contained in:
Sveta Smirnova
2024-04-06 12:46:55 +03:00
parent 02664694e2
commit a4c2fd3496
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bin/pt-deadlock-logger
View File

@@ -5533,7 +5533,7 @@ is undefined which means an infinite number of iterations. The tool always
exits for L<"--run-time">, regardless of the value specified for this option. exits for L<"--run-time">, regardless of the value specified for this option.
For example, the tool will exit after 1 minute with For example, the tool will exit after 1 minute with
C<--run-time 1m --iterations 4 --interval 30> because 4 iterations at 30 C<--run-time 1m --iterations 4 --interval 30> because 4 iterations at 30
second intervals would take 2 minutes, longer than the 1 mintue run-time. second intervals would take 2 minutes, longer than the 1 minute run-time.
=item --log =item --log

2
bin/pt-fk-error-logger
View File

@@ -4530,7 +4530,7 @@ is undefined which means an infinite number of iterations. The tool always
exits for L<"--run-time">, regardless of the value specified for this option. exits for L<"--run-time">, regardless of the value specified for this option.
For example, the tool will exit after 1 minute with For example, the tool will exit after 1 minute with
C<--run-time 1m --iterations 4 --interval 30> because 4 iterations at 30 C<--run-time 1m --iterations 4 --interval 30> because 4 iterations at 30
second intervals would take 2 minutes, longer than the 1 mintue run-time. second intervals would take 2 minutes, longer than the 1 minute run-time.
=item --log =item --log

2
lib/SchemaIterator.pm
View File

@@ -495,7 +495,7 @@ sub table_is_allowed {
# then we'll get d1 tables when the user only wants d2 tables. So when # then we'll get d1 tables when the user only wants d2 tables. So when
# a table passes allow filters, reaching this point, meaning it is allowed, # a table passes allow filters, reaching this point, meaning it is allowed,
# we make this final to check to see if it's allowed in any database (*) # we make this final to check to see if it's allowed in any database (*)
# or allowed in the specific database that the user qualifed the table with. # or allowed in the specific database that the user qualified the table with.
# The first two checks are to prevent auto-vivifying the filters which will # The first two checks are to prevent auto-vivifying the filters which will
# cause bad results (see a similar comment in _make_filters()). # cause bad results (see a similar comment in _make_filters()).
if ( $filter->{'tables'} if ( $filter->{'tables'}