TimescaleDB is implemented as an extension on Postgres, so native Postgres runs underneath. ("Underneath is not really the right way to think about it, because

TimescaleDB is implemented as an extension on Postgres, so native Postgres runs underneath. ("Underneath is not really the right way to think about it, because the extension model lets us hook into lots of different places in the Postgres code -- TimescaleDB generates a shared library .so, implemented in C, so runs in same process/memory space.) But, the great thing of this is as Postgres improves, so does TimescaleDB. TimescaleDB launched with Postgres 9.6, and now supports Postgres 13 and all the great improvements that have been implemented between those two PG versions.