diff options
| author | Evan Read <eread@gitlab.com> | 2018-11-13 03:39:21 +0300 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2018-11-13 03:53:38 +0300 |
| commit | 20146580a0618e7c9a726c6d53e51d3ca60b63e8 (patch) | |
| tree | 5d70d8989f3897f84468dde83ca9521d759fc12c /doc/development/adding_database_indexes.md | |
| parent | dbb342d4d95d24a1313c64be4a923ea5f759d3fa (diff) | |
Resolve Markdown ordered lists not conforming to styleguide
Diffstat (limited to 'doc/development/adding_database_indexes.md')
| -rw-r--r-- | doc/development/adding_database_indexes.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/adding_database_indexes.md b/doc/development/adding_database_indexes.md index ea6f14da3b9..d1d2b8c4907 100644 --- a/doc/development/adding_database_indexes.md +++ b/doc/development/adding_database_indexes.md @@ -28,9 +28,9 @@ to filter data by. Instead one should ask themselves the following questions: 1. Can I write my query in such a way that it re-uses as many existing indexes as possible? -2. Is the data going to be large enough that using an index will actually be +1. Is the data going to be large enough that using an index will actually be faster than just iterating over the rows in the table? -3. Is the overhead of maintaining the index worth the reduction in query +1. Is the overhead of maintaining the index worth the reduction in query timings? We'll explore every question in detail below. @@ -62,7 +62,7 @@ In short: 1. Try to write your query in such a way that it re-uses as many existing indexes as possible. -2. Run the query using `EXPLAIN ANALYZE` and study the output to find the most +1. Run the query using `EXPLAIN ANALYZE` and study the output to find the most ideal query. ## Data Size |