Repository navigation
Conversation
Test plans for use-time-buckets, time-and-continuous-aggregates and primary-keys-time-and-uniqueness. Each passes on a self-hosted box and, through psql, on a Tiger Cloud service (TimescaleDB 2.32.0). time-and-continuous-aggregates: - Insert rows before creating the view. The view returned 0 rows because it was created empty and never refreshed. - Regenerate the sample output: it showed buckets of 5, the view buckets by 500. - Intro: timezone-dependent functions give a warning from 2.20.0, and an error inside time_bucket and in earlier versions. - Make the cast a real second method, on a view that stores timestamptz. On the first view it did nothing. - Integer time: seconds throughout, chunk interval of one day. The interval of 10 made 1,001 chunks for 10,000 rows. _old-api-create-hypertable: - With several timestamp columns the first is used; there is no error. The error is for a table with none. - Write the option as tsdb.partition_column; the bare name fails. - Point the 2.20.0 and 2.22.1 links at their own releases.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
✅ Checklist CompleteThank you for taking the time to properly review your PR! All checklist items are complete. |
Contributor
|
✅ Link check passed on this preview. Link check: https://tiger-data-docs-huaff6182-tigerdata.vercel.app745 pages scanned, 6668 unique internal links checked.
|
atovpeko
marked this pull request as draft
November 16, 2026 13:48
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe your changes
Test plans for
use-time-buckets,time-and-continuous-aggregatesandprimary-keys-time-and-uniqueness. Each passes on a self-hosted box and, through psql, on a Tiger Cloud service (TimescaleDB 2.32.0). Fixes the plans found:time-and-continuous-aggregatesinserts rows before creating the view (it returned 0 rows), shows real sample output, scopes the timezone warning to 2.20.0 and later, turns the no-op cast into a working second method, and uses seconds with a one-day chunk interval._old-api-create-hypertableno longer claims an error for several timestamp columns, writestsdb.partition_column, and links 2.20.0 and 2.22.1 to their own releases.Draft until the doc-testing tool reruns the three plans on Tiger Cloud.
Affected pages
/build/tips-and-tricks/troubleshoot-continuous-aggregates
/learn/continuous-aggregates/time-and-continuous-aggregates
/learn/data-lifecycle/time-buckets/use-time-buckets
/learn/data-model/primary-keys-time-and-uniqueness
/reference/timescaledb/hypercore/add_columnstore_policy
/reference/timescaledb/hypertables
/reference/timescaledb/hypertables/create_table
🧪 Component kitchen sink — check for visual regressions if you changed components, styles, or dependencies.
Related Issues
Issue: none
Checklist before requesting a review