percona/percona-toolkit
1
0
Fork 0
mirror of https://github.com/percona/percona-toolkit.git synced 2025-12-10 02:01:17 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix some spelling errors (#462)

Browse Source 
Co-authored-by: Sveta Smirnova <svetasmirnova@users.noreply.github.com>
This commit is contained in:
Dario Minnucci
2022-12-01 13:54:24 +01:00
committed by GitHub
parent e8977042d4
commit 7e5c51d0fb
7 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bin/pt-kill
View File

@@ -7874,7 +7874,7 @@ type: DSN
Store each query killed in this DSN.
The argument specifies a table to store all killed queries. The DSN
passed in must have the databse (D) and table (t) options. The
passed in must have the database (D) and table (t) options. The
table must have at least the following columns. You can add more columns for
your own special purposes, but they won't be used by pt-kill. The
following CREATE TABLE definition is also used for L<"--create-log-table">.

2
bin/pt-online-schema-change
View File

@@ -12073,7 +12073,7 @@ C<wsrep_OSU_method> is not C<TOI>. There is no way to disable these checks.
=head1 MySQL 5.7 + Generated columns
The tools ignores MySQL 5.7+ C<GENERATED> columns since the value for those columns
is generated according to the expresion used to compute column values.
is generated according to the expression used to compute column values.
=head1 OUTPUT

0
bin/pt-query-digest Executable file → Normal file
View File

4
bin/pt-summary
View File

@@ -2223,7 +2223,7 @@ report_system_summary () { local PTFUNCNAME=report_system_summary;
name_val "${disk}" "${scheduler:-"UNREADABLE"}"
done
section "Disk Partioning"
section "Disk Partitioning"
parse_fdisk "$data_dir/partitioning"
section "Kernel Inode State"
@@ -2516,7 +2516,7 @@ C<df>. This section is skipped if you disable L<"--summarize-mounts">.
The disk scheduler information is extracted from the F</sys> filesystem in
Linux.
# Disk Partioning ############################################
# Disk Partitioning ######################################
Device Type Start End Size
============ ==== ========== ========== ==================
/dev/sda Disk 17179869184

6
bin/pt-table-checksum Executable file → Normal file
View File

@@ -11492,7 +11492,7 @@ sub main {
TABLE:
while ( $oktorun && $have_time->() && (my $tbl = $schema_iter->next()) ) {
eval {
# Results, stats, and info related to checksuming this table can
# Results, stats, and info related to checksumming this table can
# be saved here. print_checksum_results() uses this info.
$tbl->{checksum_results} = {};
@@ -13105,7 +13105,7 @@ type: string
Channel name used when connected to a server using replication channels.
Suppose you have two masters, master_a at port 12345, master_b at port 1236 and
a slave connected to both masters using channels chan_master_a and chan_master_b.
If you want to run pt-table-sync to syncronize the slave against master_a, pt-table-sync
If you want to run pt-table-sync to synchronize the slave against master_a, pt-table-sync
won't be able to determine what's the correct master since SHOW SLAVE STATUS
will return 2 rows. In this case, you can use --channel=chan_master_a to specify
the channel name to use in the SHOW SLAVE STATUS command.
@@ -13123,7 +13123,7 @@ See "Replicas using row-based replication" under L<"LIMITATIONS">.
This option modifies the behavior of L<"--create-replicate-table"> such that the
replicate table's upper and lower boundary columns are created with the BLOB
data type.
This is useful in cases where you have trouble checksuming tables with keys that
This is useful in cases where you have trouble checksumming tables with keys that
include a binary data type or that have non-standard character sets.
See L<"--replicate">.

2
bin/pt-table-sync
View File

@@ -12199,7 +12199,7 @@ type: string
Channel name used when connected to a server using replication channels.
Suppose you have two masters, master_a at port 12345, master_b at port 1236 and
a slave connected to both masters using channels chan_master_a and chan_master_b.
If you want to run pt-table-sync to syncronize the slave against master_a, pt-table-sync
If you want to run pt-table-sync to synchronize the slave against master_a, pt-table-sync
won't be able to determine what's the correct master since SHOW SLAVE STATUS
will return 2 rows. In this case, you can use --channel=chan_master_a to specify
the channel name to use in the SHOW SLAVE STATUS command.

6
bin/pt-upgrade
View File

@@ -10697,7 +10697,7 @@ on the new version of MySQL.
pt-upgrade executes queries from slow, general, binary, tcpdump, and
"raw" logs on two servers, compares many aspects of each query's exeuction
and results, and reports any signficant differences. The two servers are
and results, and reports any significant differences. The two servers are
typically development servers, one running the current production version
of MySQL and the other running the new version of MySQL.
@@ -10785,7 +10785,7 @@ network intensive. It executes queries as fast as possible.
=head1 QUERY DIFFERENCES
Signficant query differences are determined by comparing these aspects
Significant query differences are determined by comparing these aspects
of each query from both hosts:
=over
@@ -11137,7 +11137,7 @@ should be printed, in percentage, seconds, or number of iterations.
default: yes
Execute only C<SELECT> and C<SET> statements. If C<--no-read-only> is
specified, I<all> queries are exeucted: C<DROP>, C<DELETE>, C<UPDATE>, etc.
specified, I<all> queries are executed: C<DROP>, C<DELETE>, C<UPDATE>, etc.
Even when running in default read-only mode, you should use a MySQL user
with only C<SELECT> privileges to insure against bugs in the tool.