Skip to content

Latest commit

 

History

History
127 lines (85 loc) · 9.35 KB

CHANGELOG.md

File metadata and controls

127 lines (85 loc) · 9.35 KB
Raw

v0.9.0

New features

  • The logs will be colored only when on a tty or when --log-color is provided (#416)
  • Now the store prefix is configurable --store-prefix (#425)

BugFixes

  • Fixed keeper missing waits for instance ready (#418)
  • Fixed etcdv3 store wrong get leader timeout causing stolonctl status errors (#426)

Thanks to everybody who contributed to this release:

Pierre Fersing, Dmitry Andreev

v0.8.0

New features

  • Added support for etcd v3 api (using --store-backend etcdv3) (#393)
  • Now the stolon-proxy has tcp keepalive enabled by default and provides options for tuning its behavior (#357)
  • Added removekeeper command to stolonctl (#383)
  • Added the ability to choose the authentication method for su and replication user (currently one of md5 or trust) (#380)

BugFixes

  • Fixed and improved db startup logic to handle a different pg_ctl start behavior between postgres 9 and 10 (#401)
  • Fixed keeper datadir locking (#405)

and many other bug fixes and documentation improvements.

Thanks to everybody who contributed to this release:

AmberBee, @emded, Pierre Fersing

v0.7.0

New features

  • Added ability to define custom pg_hba.conf entries (#341)
  • Added ability to set Locale, Encoding and DataChecksums when initializing a new pg db cluster (#338)
  • Added stolonctl clusterdata command to dump the current clusterdata saved in the store (#318)
  • Detect if a standby cannot sync due to missing wal files on primary (#312)
  • Various improvements to proxy logic (#308) (#310)
  • Added cluster spec option to define additional wal senders (#311)
  • Added various postgresql recovery target settings for point in time recovery (#303)
  • Added --log-level argument to stolon commands (deprecating --debug) (#298)

BugFixes

  • IPV6 fixes (#326)
  • Handle null values in pg_file_settings view (#322)

and many other bug fixes and documentation improvements

Thanks to everybody who contributed to this release:

Albert Vaca, @emded, Niklas Hambüchen, Tim Heckman

v0.6.0

This version introduces various interesting new features (like support for upcoming PostgreSQL 10 and standby cluster) and different bug fixes.

New features

  • Support for PostgreSQL 10 (#281)
  • Standby cluster (for multi site disaster recovery and near zero downtime migration) (#283)
  • Old dead keeper removal (#280)
  • On asynchronous clusters elect master only if behind a user defined lag (#268)
  • Docker standalone, swarm and compose examples (#231) and (#238)

BugFixes

  • Fix incorrect parsing of synchronous_standby_names when using synchronous replication with two or more synchronous standbys (#264)
  • Fix non atomic writes of local state files (#265)

and many other

Thanks to everybody who contributed to this release:

Alexander Ermolaev, Dario Nieuwenhuis, Euan Kemp, Ivan Sim, Jasper Siepkes, Niklas Hambüchen, Sajal Kayan

v0.5.0

This version is a big step forward previous releases and provides many new features and a better cluster management.

  • Now the configuration is fully declarative (see cluster specification documentation) (#178).
  • Ability to create a new cluster starting from a previous backup (point in time recovery) (#183)
  • Wal-e backup/restore example (#183)
  • Better synchronous replication, the user can define a min and a max number of required synchronous standbys and the master will always block waiting for acknowledge by the required sync standbys. Only synchronous standbys will be elected as new master. (#219)
  • Production ready kubernetes examples (just change the persistent volume provider) (#215)
  • To keep an unique managed central configuration, the postgresql parameters can now only be managed only using the cluster specification (#181)
  • When (re)initializing a new cluster (with an empty db, from an existing instance or from a backup) the postgresql parameters are automatically merged in the cluster spec (#181)
  • Use only store based communication and discovery (removed all the kubernetes specific options) (#195)
  • Ability to use TLS communication with the store (for both etcd and consul) (#208)
  • Better standby monitoring and replacement (#218)
  • Improved logging (#187)

Many other improvements and bug fixes

v0.4.0

Some cleanups and changes in preparation for release v0.5.0 that will receive a big refactor (with different breaking changes) needed to bring a lot of new features.

v0.3.0

  • Support multiple stores via libkv (#102). Currently etcd and consul are supported.
  • Can use pg_rewind to sync slaves instead of doing a full resync (#122).
  • The --initial-cluster-config option has been added to the stolon-sentinel to provide an initial cluster configuration (#107).
  • A cluster config option for initializing the cluster also if multiple keepers are registred has been added (#106). By default a sentinel won't initialize a new if multiple keepers are registered since it cannot know which one should be the master. With this option a random keeper will be choosed as the master. This is useful when an user wants to create a new cluster with an empty database and starting all the keeper together instead of having to start only one keeper, wait it to being elected as master and then starting the other keepers.
  • The --discovery-type option has been added to the stolon-sentinel to choose if keeper discovery should be done using the store or kubernetes (#129).
  • Various options has been added to the stolon-keeper for setting postgres superuser, replication and initial superuser usernames and passwords (#136).
  • Numerous enhancements and bugfixes.

Thanks to all the contributors!

v0.2.0

  • A stolon client (stolonctl) is provided. At the moment it can be used to get clusters list, cluster status and get/replace/patch cluster config (#28 #64). In future multiple additional functions will be added. See doc/stolonctl.md.
  • The cluster config is now configurable using stolonctl (#2). See doc/cluster_config.md.
  • Users can directly put their preferred postgres configuration files inside a configuration directory ($dataDir/postgres/conf.d or provided with --pg-conf-dir) (see doc/postgres_parameters.md)
  • Users can centrally manage global postgres parameters. They can be configured in the cluster configuration (see doc/postgres_parameters.md)
  • Now the stolon-proxy closes connections on etcd error. This will help load balancing multiple stolon proxies (#74 #76 #80).
  • kubernetes: added readiness probe for stolon proxy (#82)
  • The keeper takes an exclusive fs lock on its datadir (#48)
  • Numerous bug fixes and improved tests.