Update for tiering on azure #4658
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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-azure-data-tiering |
steve-tsdb
reviewed
Feb 6, 2026
steve-tsdb
reviewed
Feb 6, 2026
steve-tsdb
reviewed
Feb 6, 2026
| | Dynamic I/O provisioning for high-read/ high-write performance | <span style="color:green">✓</span> | <span style="color:green">✓</span> | Manual | | ||
| | Low-cost storage with infinite capacity on S3 | <span style="color:green">✓</span> | <span style="color:red">✗</span> | <span style="color:red">✗</span> | | ||
| | Transparent queries across high-performance and low-cost tiers | <span style="color:green">✓</span> | <span style="color:red">✗</span> | <span style="color:red">✗</span> | | ||
| | Low-cost storage with infinite capacity on S3 | <span style="color:green">✓</span> | <span style="color:green">✓</span> | <span style="color:red">✗</span> | |
There was a problem hiding this comment.
on cloud object storage (rather than S3)
Contributor
Author
There was a problem hiding this comment.
Do we want to remove all mentions of S3 then? If so, this has to be coordinated with marketing as well, because it's definitely on the pricing page: https://www.tigerdata.com/pricing (and across other places in docs)
steve-tsdb
reviewed
Feb 6, 2026
steve-tsdb
reviewed
Feb 6, 2026
steve-tsdb
left a comment
steve-tsdb
left a comment
There was a problem hiding this comment.
couple minor comments/suggestions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed notes about tiered storage not available for Azure, so there are now generic pages about tiering: https://docs-dev.timescale.com/docs-azure-data-tiering/use-timescale/azure-data-tiering/data-tiering/ The only note is left for enhanced storage, which is not available on Azure.