Skip to content

Clarify hypercore migration guidance for existing hypertables#292

Open
atovpeko wants to merge 2 commits into
mainfrom
atovpeko1/edu-131-clarify-hypercore-migration-guidance-for-existing
Open

Clarify hypercore migration guidance for existing hypertables#292
atovpeko wants to merge 2 commits into
mainfrom
atovpeko1/edu-131-clarify-hypercore-migration-guidance-for-existing

Conversation

@atovpeko
Copy link
Copy Markdown
Collaborator

@atovpeko atovpeko commented May 27, 2026

Describe your changes

Adds an "Enable hypercore on an existing hypertable" section to setup-hypercore.mdx covering the two recommended paths for converting a populated hypertable to the columnstore:

  • Hands-off: add_columnstore_policy (notes the policy runs single-threaded and may lag on a large backlog).
  • Manual: convert_to_columnstore per chunk, with an explicit parallel-sessions sample for faster initial migration.

Also adds a warning callout explaining that conversion takes an ExclusiveLock on the chunk and contends with concurrent backfill — links to the existing pause-backfill-reconvert workflow on convert_to_rowstore.

Extends the convert_to_columnstore reference page with a bulk-migration sample showing the same parallel pattern.

Why: Review feedback flagged that the docs were missing recommended paths for migrating existing hypertables and didn't mention lock contention between conversion and backfill. Behavior was verified against the TimescaleDB 2.27.0 source (tsl/src/compression/api.c:658 for ExclusiveLock, sql/policy_internal.sql:93-121 for the serial policy loop) and end-to-end on a live Tiger Cloud service.

Affected pages

Related Issues

Issue: #EDU-131

Checklist before requesting a review

  • - This is ready for review. If not, raise as a draft PR
  • - I have reviewed my changes.
  • - I have confirmed the content is technically accurate.
  • - I have tested any code that is added or updated on the latest available version.
  • - I have confirmed the content is free of typos or grammar errors.
  • - I have verified all images and videos are clear and match production (or dev for unreleased features).
  • - This references a feature that is public. If not, add a note and we can schedule the merge for after the feature release.

@atovpeko atovpeko requested a review from a team May 27, 2026 12:34
@github-actions
Copy link
Copy Markdown

✅ Checklist Complete

Thank you for taking the time to properly review your PR! All checklist items are complete.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tiger-data-docs Error Error May 27, 2026 12:56pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant