Percona Toolkit moved to https://jira.percona.com/projects/PT

  1. Bug #1593123
  2. Comment #1

Comment 1 for bug 1593123

Revision history for this message
Sveta Smirnova (svetasmirnova) wrote :

Thank you for the report.

Verified as described with versions 2.2.20 and 3.0.2.

To repeat:

- Create 2 tables, parent and child
- Produce any FK error, so it stays in SHOW ENGINE INNODB STATUS
- Do not do any other job on the server
- Wait at least 15 seconds after the tool prints the error first time and you will see it will print it again and again

This behavior is different from the documented at https://www.percona.com/doc/percona-toolkit/3.0/pt-fk-error-logger.html: " Foreign key errors are uniquely identified by their timestamp. Only new (more recent) errors are printed or saved."