TimescaleDB: hypertables, columnstore and rollups in PostgreSQL

Scroll or pinch to zoom, drag to move, double-click to zoom in 100% SVG PNG Back to the post

TimescaleDB architecture: an ingest client inserts rows into a hypertable split into time chunks; a compression policy moves older chunks to the columnstore; a continuous aggregate summarises the hypertable and a refresh policy keeps it current; a query client reads the aggregate; every change goes to the write-ahead log, which streams to a standby replica and is archived to object storage by CloudNativePG; background jobs run the policies.