Update docs for pqd, make --create-review-tables work by default

This commit is contained in:
Brian Fraser
2013-01-30 17:35:40 -03:00
parent 3b6303f421
commit dbbb699831
+17 -9
View File
@@ -15284,7 +15284,8 @@ Analyze, aggregate, and report on a slow query log:
Review a slow log, saving results to the test.query_review table in a MySQL
server running on host1. See L<"--review"> for more on reviewing queries:
pt-query-digest --review h=host1,D=test,t=query_review /path/to/slow.log
pt-query-digest --review h=host1 --review-table test.query_review
--history-table test.query_history /path/to/slow.log
Print the structure of events so you can construct a complex L<"--filter">:
@@ -15314,7 +15315,7 @@ is safe to run even on production systems, but you might want to monitor it
until you are satisfied that the input you give it does not cause undue load.
Various options will cause pt-query-digest to insert data into tables, execute
SQL queries, and so on. These include the L<"--review"> options.
SQL queries, and so on. These include the L<"--review"> option.
At the time of this release, we know of no bugs that could cause serious harm
to users.
@@ -15795,7 +15796,9 @@ Continue parsing even if there is an error. The tool will not continue
forever: it stops once any process causes 100 errors, in which case there
is probably a bug in the tool or the input is invalid.
=item --create-review-tables
=item --[no]create-review-tables
default: yes
Create the L<"--review"> tables if they do not exist.
@@ -16305,10 +16308,15 @@ type: DSN
Store a sample of each class of query in this DSN, plus historical values
for review trend analysis
The argument specifies a table to store all unique query fingerprints in. 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-query-digest. The
following CREATE TABLE definition is also used for L<"--create-review-table">.
The argument specifies a host to store all unique query fingerprints in; the
databases and tables were this data is stored can be specified with the
L<"--review-table"> and L<"--history-table"> options.
By default, if the table doesn't exist the tool mtries creating it; This
behavior can bhe controlled with the L<"--[no]create-review-tables"> option.
If the table was created manually, it 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-query-digest. The following CREATE TABLE definition is also used by
L<"--no-create-review-tables">.
=for comment ignore-pt-internal-value
MAGIC_create_review:
@@ -16346,7 +16354,7 @@ fingerprint. This option depends on C<--group-by fingerprint> (which is the
default). It will not work otherwise.
Additionally, pt-query-digest will save information into a review table,
Additionally, pt-query-digest will save historical information into a review table,
so you can see how classes of queries have changed over time. You can
change the destination table with the L<"--history-table">
@@ -16379,7 +16387,7 @@ you could also just add a ts_min column and make it a DATE type, so you'd get
one row per class of queries per day.
The default table structure follows. The following table definition is used
for L<"--create-review-tables">:
for L<"--[no]create-review-tables">:
=for comment ignore-pt-internal-value
MAGIC_create_review_history