From 3101f4b86220a11c5ed3bccf4582dfa3de1f1879 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Thu, 7 Mar 2024 15:39:28 +0900 Subject: [PATCH] Improve README.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per report from Emre Sevinç for a typo, reworked largely by me in passing. Backpatch down to v14, where this file has been introduced. Per pull request #176. Backpatch-through: 14 --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 6a4edd20..7330a86d 100644 --- a/README.md +++ b/README.md @@ -3,12 +3,12 @@ `pg_hint_plan` makes it possible to tweak PostgreSQL execution plans using so-called "hints" in SQL comments, like `/*+ SeqScan(a) */`. -PostgreSQL uses a cost-based optimizer, which utilizes data statistics, not -static rules. The planner (optimizer) esitimates costs of each possible -execution plans for a SQL statement then the execution plan with the lowest -cost finally be executed. The planner does its best to select the best best -execution plan, but is not always perfect, since it doesn't count some -properties of the data, for example, correlation between columns. +PostgreSQL uses a cost-based optimizer, that uses data statistics, not static +rules. The planner (optimizer) estimates costs of each possible execution +plans for a SQL statement, then executes the plan with the lowest cost. +The planner does its best to select the best execution plan, but it is far +from perfect, since it may not count some data properties, like correlation +between columns. For more details, please see the various documentations available in the **docs/** directory: