Skip to content

Remove hypercore table access method #8364

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 9, 2025
Merged

Remove hypercore table access method #8364

merged 1 commit into from
Jul 9, 2025

Conversation

@svenklemm
Copy link
Member

The hypercore table access method was an experiment that did not
show the signals we hoped for so with 2.22 it will no longer be
available. Any upgrade from previous versions with relations using
the hypercore table access method will be blocked.

@codecov
Copy link

codecov bot commented Jul 8, 2025 •
edited
Loading

Codecov Report

❌ Patch coverage is 94.44444% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.85%. Comparing base (8b97f9b) to head (de3e913).
⚠️ Report is 148 commits behind head on main.

Files with missing lines Patch % Lines
src/process_utility.c 87.50% 1 Missing ⚠️
tsl/src/nodes/vector_agg/exec.c 88.88% 0 Missing and 1 partial ⚠️
Additional details and impacted files 
@@            Coverage Diff             @@
##             main    #8364      +/-   ##
==========================================
- Coverage   82.28%   81.85%   -0.44%     
==========================================
  Files         262      246      -16     
  Lines       49075    45693    -3382     
  Branches    12362    11538     -824     
==========================================
- Hits        40383    37402    -2981     
+ Misses       3749     3746       -3     
+ Partials     4943     4545     -398

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@svenklemm svenklemm force-pushed the sven/tam_removal branch 5 times, most recently from c6a8d05 to 83b42e0 Compare July 8, 2025 20:42
@svenklemm svenklemm added this to the v2.22.0 milestone Jul 9, 2025
@svenklemm svenklemm added the tech-debt Needs refactoring and improvement tasks related to the source code and its architecture. label Jul 9, 2025
@svenklemm
Remove hypercore table access method
de3e913 
The hypercore table access method was an experiment that did not
show the signals we hoped for so with 2.22 it will no longer be
available. Any upgrade from previous versions with relations using
the hypercore table access method will be blocked.
@svenklemm svenklemm merged commit e444ddf into main Jul 9, 2025
40 checks passed
@svenklemm svenklemm deleted the sven/tam_removal branch July 9, 2025 10:04
This was referenced Jul 31, 2025
Closed
Closed
Closed
Closed
Closed
@svenklemm svenklemm mentioned this pull request Aug 26, 2025
Merged
philkra pushed a commit that referenced this pull request Sep 2, 2025
@timescale-automation
Release 2.22.0 (#8536)
bf4cea8 
## 2.22.0 (2025-09-02)

This release contains performance improvements and bug fixes since the 2.21.3 release. We recommend that you upgrade at the next available opportunity.

**Highlighted features in TimescaleDB v2.22.0**
* Sparse indexes on compressed hypertables can now be explicitly configured via `ALTER TABLE` rather than relying only on internal heuristics. Users can define indexes on multiple columns to improve query performance for their specific workloads.
* [Tech Preview] Continuous aggregates now support the `timescaledb.invalidate_using` option, enabling invalidations to be collected either via triggers on the hypertable or directly from WAL using logical decoding. Aggregates inherit the hypertable’s method if none is specified.  
* UUIDv7 compression and vectorization are now supported. The compression algorithm leverages the timestamp portion for delta-delta compression while storing the random portion separately. The vectorized equality/inequality filters with bulk decompression deliver ~2× faster query performance. The feature is disabled by default (`timescaledb.enable_uuid_compression`) to simplify the downgrading experience, and will be enabled out of the box in the next minor release.
* Hypertables can now be partitioned by UUIDv7 columns, leveraging their embedded timestamps for time-based chunking. We’ve also added utility functions to simplify working with UUIDv7, such as generating values or extracting timestamps - e.g., `uuid_timestamp()` returns a PostgreSQL timestamp from a UUIDv7.
* SkipScan now supports multi-column indexes in not-null mode, improving performance for distinct and ordered queries across multiple keys.  

**Removal of the hypercore table access method**
We made the decision to deprecate the hypercore table access method (TAM) with the 2.21.0 release. Hypercore TAM was an experiment and it did not show the performance improvements we hoped for. It is removed with this release. Upgrades to 2.22.0 and higher are blocked if TAM is still in use. Since TAM’s inception in [2.18.0](https://github.com/timescale/timescaledb/releases/tag/2.18.0), we learned that btrees were not the right architecture. Recent advancements in the columnstore, such as more performant backfilling, SkipScan, adding check constraints, and faster point queries, put the [columnstore](https://www.timescale.com/blog/hypercore-a-hybrid-row-storage-engine-for-real-time-analytics) close to or on par with TAM without needing to store an additional index. We apologize for the inconvenience this action potentially causes and are here to assist you during the migration process.

Migration path

```
do $$
declare
   relid regclass;
begin
   for relid in
       select cl.oid from pg_class cl
       join pg_am am on (am.oid = cl.relam)
       where am.amname = 'hypercore'
   loop
       raise notice 'converting % to heap', relid::regclass;
       execute format('alter table %s set access method heap', relid);
   end loop;
end
$$;
```

**Features**
* [#8247](#8247) Add configurable alter settings for sparse indexes
* [#8306](#8306) Add option for invalidation collection using WAL for continuous aggregates
* [#8340](#8340) Improve selectivity estimates for sparse minmax indexes, so that an index scan on a table in the columnstore is chosen more often when it's beneficial.
* [#8360](#8360) Continuous aggregate multi-hypertable invalidation processing
* [#8364](#8364) Remove hypercore table access method
* [#8371](#8371) Show available timescaledb `ALTER` options when encountering unsupported options
* [#8376](#8376) Change `DecompressChunk` custom node name to `ColumnarScan`
* [#8385](#8385) UUID v7 functions for testing pre PG18
* [#8393](#8393) Add specialized compression for UUIDs. Best suited for UUID v7, but still works with other UUID versions. This is experimental at the moment and backward compatibility is not guaranteed.
* [#8398](#8398) Set default compression settings at compress time
* [#8401](#8401) Support `ALTER TABLE RESET` for compression settings
* [#8414](#8414) Vectorised filtering of UUID Eq and Ne filters, plus bulk decompression of UUIDs
* [#8424](#8424) Block downgrade when orderby setting is `NULL`
* [#8454](#8454) Remove internal unused index helper functions
* [#8494](#8494) Improve job stat history retention policy
* [#8496](#8496) Fix dropping chunks with foreign keys
* [#8505](#8505) Add support for partitioning on UUIDv7
* [#8513](#8513) Support multikey SkipScan when all keys are guaranteed to be non-null
* [#8514](#8514) Concurrent continuous aggregates improvements
* [#8528](#8528) Add the `_timescaledb_functions.chunk_status_text` helper function
* [#8529](#8529) Optimize direct compress status handling

**Bugfixes**
* [#8422](#8422) Don't require `columnstore=false` when using the TimescaleDB Apache 2 Edition
* [#8493](#8493) Change log level of `not null` constraint message
* [#8500](#8500) Fix uniqueness check with generated columns and hypercore
* [#8545](#8545) Fix error in LOCF/Interpolate with out-of-order and repeated columns
* [#8558](#8558) Error out on bad args when processing invalidation
* [#8559](#8559) Fix `timestamp out of range` using `end_offset=NULL` on CAgg refresh policy

**GUCs**
* `enable_multikey_skipscan`: Enable SkipScan for multiple distinct keys, default: on
* `enable_uuid_compression`: Enable UUID compression functionality, default: off
* `cagg_processing_wal_batch_size`: Batch size when processing WAL entries, default: 10000
* `cagg_processing_low_work_mem`: Low working memory limit for continuous aggregate invalidation processing, default: 38.4MB
* `cagg_processing_high_work_mem`: High working memory limit for continuous aggregate invalidation processing, default: 51.2MB

**Thanks**
* @CodeTherapist for reporting an issue where foreign key checks did not work after several insert statements
* @moodgorning for reporting a bug in queries with LOCF/Interpolate using out-of-order columns
* @nofalx for reporting an error when using `end_offset=NULL` on CAgg refresh policy
* @pierreforstmann for fixing a bug that happened when dropping chunks with foreign keys
* @Zaczero for reporting a bug with CREATE TABLE WITH when using the TimescaleDB Apache 2 Edition
@timescale-automation timescale-automation added the released-2.22.0 Released in 2.22.0 label Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Poroma-Banerjee Poroma-Banerjee Poroma-Banerjee approved these changes

@akuzm akuzm akuzm approved these changes

@antekresic antekresic Awaiting requested review from antekresic

Assignees

@svenklemm svenklemm

Labels

released-2.22.0 Released in 2.22.0 tech-debt Needs refactoring and improvement tasks related to the source code and its architecture.

Projects

None yet

Milestone

v2.22.0

Development

Successfully merging this pull request may close these issues.

4 participants

@svenklemm @Poroma-Banerjee @akuzm @timescale-automation