...
SHOW_HANDLE [table/database/structure_definition HOBJ] or [table mask] | Shows information on open descriptors. For more information see the chapter DBManager - debugging. |
SHOW_CONNECT [database HOBJ [connect/transaction ID]] or [database mask [connect ID]] [DETAIL] | Shows information on open connections. For more information see the chapter DBManager - debugging. |
SET_WATCHDOG database_mask seconds [NONTRANS] | Switches on the monitoring of connections that perform SQL commands longer than the specified time seconds. This information can be used for the profiling of applications and for the detection of slow SQL commands. If a NONTRANS clause is specified, transactional connections are not monitored. Starting with version 10.1.39, after the long-running SQL is finished, detailed info about it is written to a log file. More information can be found in chapter D2000 DBManager - debugging. |
SET_WATCHDOG_QUEUE database_mask seconds [NONTRANS] | Switches on the monitoring of database actions that take longer to be processed (including waiting in queues of DBManager) than the specified time seconds. After such a database action is finished, detailed info about it is written to a log file. If a NONTRANS clause is specified, transactional connections are not monitored. More information can be found in chapter D2000 DBManager - debugging. |
MONITOR_TRANS SHOW {ALL/<id>} [<file_path>] MONITOR_TRANS ON <history_depth_sec> MONITOR_TRANS OFF MONITOR_TRANS RESET | The mechanism for monitoring of the transactions. Columns in the list: Note: After starting DBManager, the monitoring is switched off. |
MONITOR_CONNECTS SHOW {ALL/<id>} [<file_path>] MONITOR_CONNECTS ON <history_depth_sec> MONITOR_CONNECTS OFF MONITOR_CONNECTS RESET | Monitoring the connections. Columns in the list: Note: After starting DBManager, the monitoring is activated with the time-depth history of closed connections which is 3 hours (10 800 seconds). |
TIME_STATISTICS database_mask [DETAIL] | Displays statistics of execution of individual database action types per-database or per-table (if a DETAIL parameter is specified). For more information see the chapter DBManager - debugging. |
CLEAN_STATEMENTS database_mask | This command can be used to clear the cache of precompiled statements on the PostgreSQL platform (the DEALLOCATE ALL statement is executed). Cleaning can make memory usage more efficient and, in some cases, speed up the database. |
Kotva | ||||
---|---|---|---|---|
|
...