Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Another minor formatting fix. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | schemalint |
| Files: | files | file ages | folders |
| SHA3-256: |
9fa2ce3c2b75408594d387684984cd94 |
| User & Date: | dan 2017-04-21 19:58:35 |
Context
|
2017-05-01
| ||
| 14:25 | Update this branch with latest trunk changes. (check-in: 11f4761c user: dan tags: schemalint) | |
|
2017-04-21
| ||
| 19:58 | Another minor formatting fix. (check-in: 9fa2ce3c user: dan tags: schemalint) | |
| 19:56 | Fix formatting errors in the previous commit. (check-in: da9a2e5a user: dan tags: schemalint) | |
Changes
Changes to ext/expert/README.md.
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
1. The user database schema is copied to a temporary database.
1. All SQL queries are prepared against the temporary database.
Information regarding the WHERE and ORDER BY clauses, and other query
features that affect index selection are recorded.
1. The information gathered in step 2 is used to create candidate indexes
- indexes that the planner might have made use of in the previous step,
had they been available.
1. A subset of the data in the user database is used to generate statistics
for all existing indexes and the candidate indexes generated in step 3
above.
1. The SQL queries are prepared a second time. If the planner uses any
of the indexes created in step 3, they are recommended to the user.
|
| | | |
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
1. The user database schema is copied to a temporary database.
1. All SQL queries are prepared against the temporary database.
Information regarding the WHERE and ORDER BY clauses, and other query
features that affect index selection are recorded.
1. The information gathered in step 2 is used to create candidate
indexes - indexes that the planner might have made use of in the previous
step, had they been available.
1. A subset of the data in the user database is used to generate statistics
for all existing indexes and the candidate indexes generated in step 3
above.
1. The SQL queries are prepared a second time. If the planner uses any
of the indexes created in step 3, they are recommended to the user.
|