#Timescaledb postgresql 13 how to
#Timescaledb postgresql 13 update
#Timescaledb postgresql 13 upgrade

env command : ports : - 0.0.0.0:5432:5432 networks : traefik-public : deploy : # Either global (exactly one container per physical node) or # replicated (a specified number of containers). postgresql_nf target : /postgresql_nf read_only : false env_file. Version : ' 3.7' services : timescale13 : # Name of the image and tag the Dockerfile creates image : timescale/timescaledb:2.3.0-pg13 volumes : - type : volume # source: timescale-db # the volume name source : timescale-db-pg13 target : /var/lib/postgresql/data # the location in the container where the data are stored read_only : false # Custom nf file will be mounted (see command: as well) - type : bind source.

Next I created a brand new “” file for my PostgreSQL v13 database.īefore I executed it, I also created a separate volume for PostgreSQL 13:

Follow those steps to create a backup in an AWS S3 bucket.

#Timescaledb postgresql 13 how to

Here’s a link to my previous post on how to automatically backup a TimescaleDB database each night to an AWS S3 bucket, using a custom Docker image I created. However, that’s got its own complications, and I didn’t want the database to be down for any length of time, so instead I backed up our existing database, then created a new PostgreSQL 13 database with a new Docker volume, and restored the backup to the new database. Here are the official instructions for upgrading PostgreSQL.

#Timescaledb postgresql 13 upgrade

This second post is about how I managed to upgrade PostreSQL to v13 from v11 while preserving all my data (which is saved in a Docker volume).

#Timescaledb postgresql 13 update

The past few days I’ve been trying to update my version of TimescaleDB from v1.6.0 to v2.3.0 (see yesterday’s post on updating the TimescaleDB extension), while also upgrading PostgreSQL from v11 to v13, since TimescaleDB v2.3.0 doesn’t support Postgres 11 anymore.