mirror of
https://github.com/percona/percona-toolkit.git
synced 2026-01-29 03:07:54 +08:00
@@ -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.
|
||||
For example, the tool will exit after 1 minute with
|
||||
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
|
||||
|
||||
|
||||
@@ -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.
|
||||
For example, the tool will exit after 1 minute with
|
||||
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
|
||||
|
||||
|
||||
@@ -495,7 +495,7 @@ sub table_is_allowed {
|
||||
# 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,
|
||||
# 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
|
||||
# cause bad results (see a similar comment in _make_filters()).
|
||||
if ( $filter->{'tables'}
|
||||
|
||||
Reference in New Issue
Block a user