|
8 | 8 | <title>Overview</title> |
9 | 9 | <para> |
10 | 10 | Each nonutility query statement (SELECT/INSERT/UPDATE/DELETE) after |
11 | | - optimization/planning stage is translated into plan tree wich is kind of |
| 11 | + optimization/planning stage is translated into plan tree, which is kind of |
12 | 12 | imperative representation of declarative SQL query. EXPLAIN ANALYZE |
13 | 13 | request allows to demonstrate execution statistics gathered from each |
14 | 14 | node of plan tree (full time of execution, number of rows emitted to upper |
|
138 | 138 | </listitem> |
139 | 139 | <listitem> |
140 | 140 | <para> |
141 | | - format - EXPLAIN format to be used for plans printing,posible values: |
| 141 | + format - EXPLAIN format to be used for plans printing,possible values: |
142 | 142 | text, xml, json, yaml. |
143 | 143 | </para> |
144 | 144 | </listitem> |
|
150 | 150 | </para> |
151 | 151 | <para> |
152 | 152 | Calling role have to be superuser or member of the role whose backend is |
153 | | - being called.Othrewise function prints ERROR message |
| 153 | + being called.Otherwise function prints ERROR message |
154 | 154 | <literal>permission denied</literal>. |
155 | 155 | </para> |
156 | 156 | </sect2> |
|