![]() Postgres | postgres | SELECT datname,usename,current_query FROM pg_stat_activity Postgres | postgres | SELECT datname,usename,query FROM pg_stat_activity ĪnalyticDB for PostgreSQL V4.3: SELECT datname,usename,current_query FROM pg_stat_activity datname | usename | current_query You can execute the following SQL statements to view current queries executed by usersĪnalyticDB for PostgreSQL V6.0: SELECT datname,usename,query FROM pg_stat_activity datname | usename | query (9 rows) Query the SQL execution information SELECT datname,usename,client_addr,client_port FROM pg_stat_activity datname | usename | client_addr | client_port You can execute the following SQL statement to view the connected users and their The amount of time for which the query has been queued. Idle in transaction (aborted), fastpath function call, and disabled. Valid values: active, idle, idle in transaction, The backend is waiting on a lock or on replication If the current query is the first transaction, this field The time when the current transaction was started. The name of the application on the client. This field can be reported by a reverse DNS lookup of The TCP port that is used for the communications between the client and the backend.Ī value of -1 indicates that a UNIX socket is used. Is an internal process such as auto-vacuum. ![]() If client_addr is left empty, the client is connected by using a UNIX socket on the server, or this The transaction ID of the current backend process. The time when the current backend process was started. If the state field is set to a value other than active, the query_start field indicates the time when the last query was started. The time when the active query was started. Indicates whether the current query is waiting on a lock. ![]() Note This field is supported only for AnalyticDB for PostgreSQL V6.0.
0 Comments
Leave a Reply. |