Skip to content

📝 Changelog entry for TimescaleDB 2.27.1 (staged for week of June 1)#291

Draft
brandonpurcell-dev wants to merge 1 commit into
changelog/timescaledb-2.27.0from
changelog/timescaledb-2.27.1
Draft

📝 Changelog entry for TimescaleDB 2.27.1 (staged for week of June 1)#291
brandonpurcell-dev wants to merge 1 commit into
changelog/timescaledb-2.27.0from
changelog/timescaledb-2.27.1

Conversation

@brandonpurcell-dev
Copy link
Copy Markdown
Contributor

@brandonpurcell-dev brandonpurcell-dev commented May 26, 2026

Describe your changes

Stages the TimescaleDB 2.27.1 changelog entry for the cloud rollout the week of June 1, 2026. Currently dated 2026-06-01; update if the actual cloud date shifts within the week.

This PR is stacked on top of #289 (2.27.0 changelog). Once #289 merges to main, retarget this PR's base from changelog/timescaledb-2.27.0main and the diff will collapse to just the 2.27.1 entry.

What's in the 2.27.1 entry

  • Tightened access controls (3 fixes): hypertable ownership before recompression (#9800), job_errors view restricted to owners (#9799), policy_reorder_remove ownership check (#9801).
  • Columnstore planner corrections (2 fixes): skip ColumnarIndexScan for GROUPING SETS / ROLLUP / CUBE (#9830) and when grouping by expression (#9828).
  • Upgrade compatibility (2 items): orphaned compression_settings cleanup during migration (#9795), composite bloom filter migration scripts (#9824).

TimescaleDB 2.27.1 was released on GitHub on May 19, 2026.

Pre-merge checklist

  • Confirm exact cloud rollout date (currently 2026-06-01)
  • Security team review on framing of the three access-control fixes
  • 📝 Changelog entry for TimescaleDB 2.27.0 #289 (2.27.0 entry) is merged
  • PR base retargeted from changelog/timescaledb-2.27.0main
  • Convert from draft → ready for review

Affected pages

Related Issues

Issue: #

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.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 26, 2026

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

Project Deployment Actions Updated (UTC)
tiger-data-docs Ready Ready Preview, Comment May 26, 2026 9:19pm

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