You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,11 @@ Each complex query statement (SELECT/INSERT/UPDATE/DELETE) after optimization/pl
7
7
8
8
In fact, this module is able to explore external backend and determine its actual state. Particularly it's helpful when backend executes a heavy query or gets stuck.
9
9
10
+
##Use cases
11
+
Using this module there can help in the following things:
12
+
- detect a long query (along with other monitoring tools)
13
+
- overwatch the query execution ([example](https://asciinema.org/a/c0jon1i6g92hnb5q4492n1rzn))
14
+
10
15
##Installation
11
16
To install`pg_query_state`, please apply patches`custom_signal.patch`,`executor_hooks.patch` and`runtime_explain.patch` to the latest stable version of PostgreSQL 9.5 and rebuild PostgreSQL.
12
17
@@ -275,5 +280,7 @@ count | 500000
275
280
```
276
281
277
282
##Feedback
283
+
Do not hesitate to post your issues, questions and new ideas at the[issues](https://github.com/postgrespro/pg_query_state/issues) page.
284
+
278
285
##Authors
279
286
Maksim Milyutin <m.milyutin@postgrespro.ru> Postgres Professional Ltd., Russia