Commit: 3c0c056b0600a143c4c33dec8a0df9f23ff48303 - pg_hint_plan (git)

firtst release

Commit MetaInfo

• Revision: 3c0c056b0600a143c4c33dec8a0df9f23ff48303 (tree)
• Zeit: 2013-06-18 09:40:09
• Autor: naoki_kishi_b1 <kishi_naoki_b1@lab....>
• Commiter: naoki_kishi_b1

Log Message

Signed-off-by: naoki_kishi_b1 <[e-mail]>

Ändern Zusammenfassung

• modified: doc/pg_hint_plan.html

Diff

--- a/doc/pg_hint_plan.html
+++ b/doc/pg_hint_plan.html
@@ -34,7 +34,7 @@
 <p>pg_hint_plan -- Tweaking planner decisions with user's hists.</p>
 
 <h2 id="synopsis">Synopsis</h2>
-<p>PostgreSQL executes queries using cost-based optimizer, and sometimes fails to choose most optimized execution plan for some types of queries.</p>
+<p>PostgreSQL executes queries using cost-based planner, and sometimes fails to choose most optimized execution plan for some types of queries.</p>
 <p>In such cases, pg_hint_plan helps users to guide the planner to choose the plans they want by putting some instructions - call them hints - in the comments prefixed to the SQL statement body. No need to rewrite statement itself nor change some GUC parameters elsewhere.</p>
 
 <h2 id="description">Description</h2>
@@ -66,10 +66,11 @@ postgres-#   ORDER BY a.aid;
 </pre>
 
 <h3 id="hint-group">Tweakable operations</h3>
-Pg_hint_plan can tweak planner for table scan methods, join methods, join orders, and temprary GUC setting during theplanner is running. For specific Hint of each group see <a href="hint_list.html">Hint list</a></p>
+Pg_hint_plan can tweak planner for table scan methods, join methods, join orders, and temprary GUC setting during the planner is running. For specific Hint of each group, see <a href="hint_list.html">Hint list</a></p>
 
 <h4>Tweaking scan method </h4>
 <p>The hint for scan methods takes one table name or alias and will instruct planner to prefer the specific scan method for the table. You can use (No)SeqScan, (No)IndexScan, (No)TidScan, (No)BitmapScan.</p>
+The hint for scan methods takes one table name or alias and will instruct planner to prefer the specific scan method for the table. You can use (No)SeqScan, (No)IndexScan, (No)TidScan, (No)BitmapScan.
 <p>These hints are applicable for ordinary tables including unlogged or temporary ones, and system catalogues. Other objects, for example, external tables, table functions, Views, CTE, or subquery results are not covered.</p>
 
 <h4>Tweaking join method</h4>