-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update indexes.md #4837
Update indexes.md #4837
Conversation
Minor style edits
@@ -10,13 +10,13 @@ DuckDB has two built-in index types. Indexes can also be defined via [extensions | |||
|
|||
### Min-Max Index (Zonemap) | |||
|
|||
A [min-max index](https://en.wikipedia.org/wiki/Block_Range_Index) (also known as zonemap and block range index) is automatically created for columns of all [general-purpose data types]({% link docs/sql/data_types/overview.md %}). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"also known as X or Y" is a bit more natural here
|
||
### Adaptive Radix Tree (ART) | ||
|
||
An [Adaptive Radix Tree (ART)](https://db.in.tum.de/~leis/papers/ART.pdf) is mainly used to ensure primary key constraints and to speed up point and very highly selective (i.e., < 0.1%) queries. ART indexes are automatically created for columns with a `UNIQUE` or `PRIMARY KEY` constraint and can be defined using `CREATE INDEX`. | ||
|
||
> Warning ART indexes must currently be able to fit in-memory during index creation. Avoid creating ART indexes if the index does not fit in memory during index creation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed unnecessary hyphen; also makes it consistent with "in memory" in the following sentence
@@ -42,7 +42,7 @@ ART indexes create a secondary copy of the data in a second location – this co | |||
`UPDATE` statements on indexed columns are transformed into a `DELETE` of the original row followed by an `INSERT` of the updated row. | |||
This rewrite has performance implications, particularly for wide tables, as entire rows are rewritten instead of only the affected columns. | |||
|
|||
Additionally, it causes the following constraint checking limitation of `UPDATE` statements. The same limitation exists in other DBMSs, like postgres. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Postgres should be uppercase
These are great! Thanks a lot! |
Minor style edits