## TL;DR

Check your compress\_segmentby choice.

## Steps

1. Check your `compress_segmentby` choice. The reporter's root cause: the segment-by date column had nearly unique values, so compression could not group rows and the compressed chunks ended up larger than the originals. Pick a low-cardinality column for `compress_segmentby` (something with few distinct values, like a device or region id) and re-test on a chunk. If the old badly-compressed chunks are no longer needed, drop them with `drop_chunks()` before decompressing and reconfiguring, so you do not keep paying for the inflated storage.

2. _Source: https://github.com/timescale/timescaledb/issues/5961 (Timescale Cloud)_

## When to use

You are seeing this: The reporter's root cause: the segment-by date column had nearly unique values, so compression could not group rows and the compressed chunks ended up larger than the originals. Use this skill when you run into "chunk size and table size increased after compression".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/timescale/timescaledb/issues/5961
