Cloning Postgres databases on Kubernetes - Oleksii Kliukin - PGCon 2022

Cloning Postgres databases on Kubernetes with Pigeobag REST, a solution that supports full and incremental backups, transparent compression, and predictable recovery time.

Key takeaways
  • Pigeobag REST is a Postgres backup and restore solution that supports full and incremental backups, and transparent compression.
  • It uses Kubernetes API to store information about the leader and uses a distributed consistency system.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni, a high availability solution, to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution uses bgbackrest to create backups and restore the database.
  • bgbackrest supports full and incremental backups, and transparent compression.
  • Pigeobag REST supports creating a restore test, which is a special type of fork that is not available in Postgres.
  • The solution uses Petroni to manage Postgres and provide predictable recovery time.
  • Petroni updates endpoints directly and can handle custom bootstraps.
  • Pigeobag REST supports creating a snapshot of the original service before upgrading, and then creating a new fork with the upgraded service.
  • It also supports creating a snapshot of the original service and then creating a new service with the same data.
  • The solution uses Kubernetes volume snapshots to create a snapshot of the original service.
  • Pigeobag REST supports creating a fork of the original service and then restoring the fork to the original service.
  • It also supports creating a fork of the original service and then using the fork to test the upgrade.
  • The solution