View Revisions: Issue #4604
Summary | 0004604: Add file containing information about blocking processes to snapshots | ||
---|---|---|---|
Revision | 2020-10-21 20:08 by emiller | ||
Description | It would be useful for snapshots to include a .csv file listing any blocking processes/queries/transactions. | ||
Revision | 2020-10-21 20:14 by emiller | ||
Description | It would be useful for snapshots to include a .csv file listing any blocking processes/queries/transactions. This file should be included in snapshots for users with MySQL, SQL Server, Postgres, Oracle, or Firebird databases at a minimum. | ||
Revision | 2020-10-27 18:54 by emiller | ||
Description | It would be useful for snapshots to include a .csv file listing any blocking processes/queries/transactions. This file should be included in snapshots for users with MySQL, SQL Server, Postgres, Oracle, or Firebird databases at a minimum. A new monitor type should also be created to make it possible to detect when SymmetricDS transactions are blocked. |
||
Revision | 2020-10-29 14:55 by emiller | ||
Description | It would be useful for snapshots to include a .csv file listing any blocking processes/queries/transactions. This file should be included in snapshots for users with MySQL, SQL Server, Postgres, Oracle, or Firebird databases at a minimum. A new monitor type should also be created to make it possible to detect when SymmetricDS transactions are blocked. Also, the details of monitor events should be made visible on the Manage Monitors screen |
||
Revision | 2020-11-06 15:48 by emiller | ||
Description | It would be useful for snapshots to include a .csv file listing any blocking processes/queries/transactions. This file should be included in snapshots for users with MySQL, SQL Server, Postgres, or Oracle databases at a minimum. A new monitor type should also be created to make it possible to detect when SymmetricDS transactions are blocked. Also, the details of monitor events should be made visible on the Manage Monitors screen |