fix docs

stalkerg · stalkerg · commit aa296c25254d · 2016-01-15T15:09:06.000+03:00
diff --git a/README.md b/README.md
@@ -1,5 +1,9 @@
 # Save and restore query plans in PostgreSQL
 
+## Rationale
+
+sr_plan looks like Oracle Outline system. It can be used to lock the execution plan. It is necessary if you do not trust the planner or able to form a better plan.
+
 ## Build
 
 Dependencies: >= Python 3.2, Mako, pycparser 
@@ -31,7 +35,7 @@ If you want to save the query plan is necessary to set the variable:
 ```SQL
 set sr_plan.write_mode = true;
 ```
-Now plans for all subsequent requests will be stored in the table sr_plans. It must be remembered that all requests will be maintained including duplicates.
+Now plans for all subsequent queries will be stored in the table sr_plans. Don't forget that all queries will be stored including duplicates.
 Making an example query:
 ```SQL
 select query_hash from sr_plans where query_hash=10;
@@ -43,12 +47,22 @@ set sr_plan.write_mode = false;
 Now verify that your query is saved:
 ```SQL
 select query_hash, enable, valid, query, explain_jsonb_plan(plan) from sr_plans;
+
+ query_hash | enable | valid |                        query                         |                 explain_jsonb_plan                 
+------------+--------+-------+------------------------------------------------------+----------------------------------------------------
+ 1783086253 | f      | t     | select query_hash from sr_plans where query_hash=10; | Bitmap Heap Scan on sr_plans                      +
+            |        |       |                                                      |   Recheck Cond: (query_hash = 10)                 +
+            |        |       |                                                      |   ->  Bitmap Index Scan on sr_plans_query_hash_idx+
+            |        |       |                                                      |         Index Cond: (query_hash = 10)             +
+            |        |       |                                                      | 
+
 ```
+
 explain_jsonb_plan function allows you to display explain execute the plan of which lies in jsonb. By default, all the plans are off, you need enable it:
 ```SQL
-update sr_plans set enable=true where query_hash=812619660;
+update sr_plans set enable=true where query_hash=1783086253;
 ```
-(812619660 for example only)
+(1783086253 for example only)
 After that, the plan for the query will be taken from the sr_plans.
 
 In addition sr plan allows you to save a parameterized query plan. In this case, we have some constants in the query are not essential.
