Backups in Managed Service for TimescaleDB

Managed Service for TimescaleDB databases are automatically backed up, with full backups daily, and write-ahead log (WAL) continuously recorded. All backups are encrypted. Managed Service for TimescaleDB uses pghoard, a PostgreSQL backup daemon and restore tool, to store backup data in cloud object stores. The number of backups stored and the retention time of the backup depends on the service plan.


The size of logical backups, and the size of the Managed Service for TimescaleDB backup that appears on the web console differs, in some cases significantly. Backup sizes that appear in the Managed Service for TimescaleDB web console are for daily backups, before encryption and compression. To view the size of each database, including space consumed by indexes, you can use the \l+ command at the psql prompt.

Differences between logical and binary backups

The two types of backups are binary backups and logical backups. Full backups are version-specific binary backups which, when combined with WAL, allow consistent recovery to a point in time (PITR). You can create a logical backup with the pg_dump command.

This table lists the differences between binary and logical backups when backing up indexes, transactions, and data:

indexcontains all data from indexesdoes not contain index data, it contains only queries used to recreate indexes from other data
transactionscontains uncommitted transactionsdoes not contain uncommitted transactions
datacontains deleted and updated rows which have not been cleaned up by PostgreSQL VACUUM process, and all databases, including templatesdoes not contain any data already deleted, and depending on the options given, the output might be compressed

Found an issue on this page?

Report an issue!

Related Content