-
Notifications
You must be signed in to change notification settings - Fork 106
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 docs about indexing #3734
base: latest
Are you sure you want to change the base?
Conversation
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-index-doc-fix |
@@ -8,8 +8,7 @@ keywords: [hypertables, indexes] | |||
# Indexing data | |||
|
|||
You can use an index on your database to speed up read operations. You can | |||
create an index on any combination of columns, as long as you include the `time` | |||
column, for time-series data. Timescale supports all table objects supported | |||
create an index on any combination of columns. Timescale supports all table objects supported | |||
within PostgreSQL, including data types, indexes, and triggers. |
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.
The bit about unique indexes is already provided further down.
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.
LGTM
Thread: https://timescaledb.slack.com/archives/C4GT3N90X/p1737381370452059