@@ -238,8 +238,8 @@ bytes). If your SQL query text look truncated, you should increase
238238| ` UP/DOWN ` | Scroll processes list |
239239| ` k/j ` | Scroll processes list |
240240| ` q ` | Quit |
241- | ` + ` | Increase refresh time. Maximum value : 5s |
242- | ` - ` | Decrease refresh time. Minimum Value : 0.5s |
241+ | ` + ` | Increase refresh time. Maximum value: 5s |
242+ | ` - ` | Decrease refresh time. Minimum Value: 0.5s |
243243| ` F1/1 ` | Running queries list |
244244| ` F2/2 ` | Waiting queries list |
245245| ` F3/3 ` | Blocking queries list |
@@ -272,15 +272,15 @@ with the `+` and `-` keys. Any query executed between two scans won't be
272272displayed.
273273
274274
275- What is more, ` pg_activity ` uses different queries to get :
275+ What is more, ` pg_activity ` uses different queries to get:
276276
277277* settings from ` pg_settings `
278278* version info using ` version() `
279279* queries and number of connections from ` pg_stat_activity `
280280* locks from ` pg_locks `
281281* tps from ` pg_database ` using ` pg_stat_get_db_xact_commit() ` and
282282 ` pg_stat_get_db_xact_rollback() `
283- * and more ( eg : ` pg_cancel_backend() ` and ` pg_terminate_backend() ` )
283+ * and more (e.g. : ` pg_cancel_backend() ` and ` pg_terminate_backend() ` )
284284
285285Those queries cannot be seen in the query tab because all queries issued from
286286the ` pg_activity ` backend are considered as noise and are not displayed . On
@@ -290,7 +290,7 @@ and `pg_stat_get_db_xact_commit()`. Therefore `pg_activity` will display a non
290290zero TPS even with no activity on the database, and/or no activity displayed on
291291screen.
292292
293- ** How can I specify a password for authentication ?**
293+ ** How can I specify a password for authentication?**
294294
295295pg_activity uses libpq to access to PostgreSQL therefore all the traditional
296296methods are available.
0 commit comments