Skip to content

Releases: zalando/spilo

standby cluster support

01 Mar 16:52
6fc3245
Compare
Choose a tag to compare
Pre-release

Added standby cluster support

Image: registry.opensource.zalan.do/acid/spilo-11:1.5-p7

Spilo-1.5-p6

25 Feb 14:49
Compare
Choose a tag to compare
  • Patroni 1.5.5
  • timescaledb 1.2.1
  • pg_stat_kcache extension is enabled by default
  • pg_stat_statements.track_utility is set of off
  • custom build wal-g (temporary, until it stabilizes)
  • better compatibility with S3-compatible storages

Spilo-1.5-p5

30 Jan 15:27
Compare
Choose a tag to compare
  • wal-g 0.2.4
  • fixed bug in the clone_with_wale.py custom bootstrap script
  • More insistent retries in the callback_role.py
  • Added after-create.sql for pg_partman, which grants some permissions on partman tables and functions to admin
  • Renamed CLONE_WAL_GSC_BUCKET to CLONE_WAL_GCS_BUCKET (fixed a typo)

Spilo-1.5-p3

16 Jan 14:20
4ac25e1
Compare
Choose a tag to compare
  • PostgreSQL 11
  • Patroni 1.5.4
  • WAL-G support
  • Automatic upgrade of TimescaleDB extension (if installed)
  • Experimental support of pg_upgrade following a custom bootstrap (this is not in place pg_upgrade of running cluster!)

Docker image: registry.opensource.zalan.do/acid/spilo-11:1.5-p3

Spilo-10:1.4-p9

06 Jul 12:46
ce79e2e
Compare
Choose a tag to compare
  • support uploading PostgreSQL logs to S3
    The new LOG_ENV_DIR, LOG_S3_BUCKET, LOG_BUCKET_SCOPE_PREFIX, LOG_BUCKET_SCOPE_SUFFIX, LOG_TMPDIR, PGLOG variables controls where the logs should be uploaded. AWSREGION can be used to choose the AWS region explicitly

  • Detect streaming replication in a way compatible with PostgreSQL 11.
    In the new version PostgreSQL the processes names in the ps list has been renamed.

  • Protect user management functions from CVE-2018-1058
    Some of the functions have security definer are owned by superuser, therefore it is very important to make sure that they are executed with search_path = 'pg_catalog'

  • Attempt to initialize roles and extensions after each promotion.
    This way we can propagate recent changes to those objects during the rolling update

  • move all scripts into the /scripts directory

Spilo-1.4-p11

06 Jul 12:56
ce79e2e
Compare
Choose a tag to compare
  • Bump up Patroni commit ID and use Patroni from the master branch
    Incorporate fixes for the enforcement of the max_worker_processes parameter on 9.3 (the parameter has been introduced only in 9.4), improve the stability of crash_recovery and consult pg_controldata on the replica during the start for parameters like max_connections that are mentioned there and can have a different value on the master. Those fixes will be a part of next Patroni release, but are important enough to use them right away.

Spilo 1.4-p10

06 Jul 12:49
ce79e2e
Compare
Choose a tag to compare
  • Fix basebackup path in the init script
    In the previous release basebackup was not running because of the typo in the script

  • Implement backup retention policy in days
    The old retention policy of using up to certain number of backups was too bad for k8s, where failovers/switchovers would happen rather often

  • Add recently added AWS regions to WAL-E

spilo-10-1.4-p8

28 May 14:14
3809c2e
Compare
Choose a tag to compare

The new image is based on Ubuntu 18.04 and includes Patroni 1.4.4 and PostgreSQL 9.3, 9.4, 9.5, 9.6 and 10

You can choose the version of PostgreSQL to run by providing PGVERSION environment variable.

Spilo-9.4-0.75-p1

30 Nov 11:59
Compare
Choose a tag to compare

New version of Spilo, incorporating Patroni 0.6 and 0.75 releases. Brings you the ability to use configurable replication_methods, tags (nofailover), the command-line client patronictl (you have to run it from inside the docker container with docker exec) and a lot of bug fixes.

The image can be obtained from registry.opensource.zalan.do/acid/spilo-9.4:0.75-p1. Note that at the moment it relies heavily on the stups.io infrastructure, particularly Taupage (which, in itself, has some other dependencies).