Skip to content

Commit

Permalink
Improve README.md
Browse files Browse the repository at this point in the history
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
  • Loading branch information
michaelpq committed Mar 7, 2024
1 parent 4b6c4c1 commit 19e01fa
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down

0 comments on commit 19e01fa

Please sign in to comment.