A PostgreSQL Docker container that automatically upgrades PostgreSQL

• docker-pgautoupgrade

  7 434 7.7 Shell

  A PostgreSQL Docker container that automatically upgrades your database

  

Warning added in https://github.com/justinclift/docker-pgautoupgrade/commit/e....

Thanks heaps. :)

• docker-postgres-upgrade

  4 992 6.5 Shell

  a PoC for using "pg_upgrade" inside Docker -- learn from it, adapt it for your needs; don't expect it to work as-is!

Related: https://github.com/tianon/docker-postgres-upgrade

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• pgsql-backup

  1 24 10.0 Shell

  PostgreSQL Backup Script. Ported from AutoMySQLBackup.

• pgkit

  7 28 7.5 Python

  Pgkit - Backup, PITR and recovery management made easy

• PostgreSQL-Disaster-Recovery-With-Barman

  1 22 10.0 Dockerfile

  A complete end-end project that demonstrates the 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features.

> The database will then start replaying the WAL files. It's progress can be tracked through the log files at /var/log/postgresql/.

- "PostgreSQL-Disaster-Recovery-With-Barman" https://github.com/softwarebrahma/PostgreSQL-Disaster-Recove... :

> The solution architecture chosen here is a 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features.

Glossary of backup terms: https://en.wikipedia.org/wiki/Glossary_of_backup_terms

Continuous Data Protection > Continuous vs near continuous:

• PostgreSQL-Disaster-Recove

  1 - -

> The database will then start replaying the WAL files. It's progress can be tracked through the log files at /var/log/postgresql/.

- "PostgreSQL-Disaster-Recovery-With-Barman" https://github.com/softwarebrahma/PostgreSQL-Disaster-Recove... :

> The solution architecture chosen here is a 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features.

Glossary of backup terms: https://en.wikipedia.org/wiki/Glossary_of_backup_terms

Continuous Data Protection > Continuous vs near continuous:

• Redash

  38 24,948 9.5 Python

  Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.

  

Yeah, a lot of the time I'd agree with you.

This container came about for the Redash project (https://github.com/getredash/redash), which has been stuck on PostgreSQL 9.5 (!) for years.

Moving to a new PostgreSQL container version is easy enough for new installations, but rolling that kind of change out to an existing userbase isn't so pretty.

For people familiar with the command line, PostgreSQL, and Docker then no worries.

But a large number of Redash deployments seem to have been done by people not skilled in those things. "We deployed it from the Digital Ocean droplet / AWS image / etc!"

For those situations, something that takes care of the database upgrade process automatically is the better approach. :)

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project