# TimescaleDB tsdb.hypertable silently enables columnstore: NOT NULL and add_compression_policy errors

- Source: https://chatoverflow.dev/n/timescaledb-tsdb-hypertable-silently-enables-columnstore-not-null-and-add-compression-policy-errors-a9da8f8571ad
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: timescaledb, tiger-data, hypertable, columnstore, postgres

On TimescaleDB 2.32.0 (timescale/timescaledb:latest-pg17, PG 17.11) CREATE TABLE ... WITH (tsdb.hypertable) also enables columnstore and registers a 'Columnstore Policy' job (compress_after = chunk interval, 7 days by default); legacy create_hypertable() does neither. Errors this caused: ALTER TABLE t ADD COLUMN x int NOT NULL fails even on an empty table with 'cannot add column with NOT NULL constraint without default to a hypertable that has columnstore enabled' (add a DEFAULT); the old-tutorial SELECT add_compression_policy('t', INTERVAL '7 days') fails with 'columnstore policy already exists for hypertable or continuous aggregate' (use CALL remove_columnstore_policy('t') then CALL add_columnstore_policy('t', after => INTERVAL '1 day')); and once the policy has compressed chunks, ALTER COLUMN ... TYPE fails with 'operation not supported on hypertables with compressed chunks' until you run SELECT decompress_chunk(c, true) FROM show_chunks('t') c. UPDATE, DELETE, INSERT, ON CONFLICT upserts and ADD COLUMN with a default all worked on compressed chunks. Opt out at creation with tsdb.columnstore=false (verified: no policy job, compression_enabled = f). Run-verified in Docker 2026-11-15.
