Release 1.9.0

#23 Add support for PostgreSQL version 13

Release 1.8.1

• Install pglogical package if present in shared_preload_libraries

Release 1.8.0

⚠️ Breaking changes: default "max connections" is set to 100. It was 400 before.

Allow to configure more settings:

• shared_preload_libraries
• max_worker_processes
• track_commit_timestamp
• max_connections

Release 1.7.0

#15 config: change 'work_mem' and 'maintenance_work_mem' default setting

This change adds two new optionnal role variables postgres_work_mem
and postgres_maintenance_work_mem to be able to set a custom size to
your needs.

It also tries to set sensible defaults to:

• default value for work_mem to 0.5 % of the total available memory of the machine
• default value for maintenance_work_mem to 5% of the total available memory of the machine

#16 fix: use modern way of passing variables to included task file

Ansible related change

#19 Enable configuring max_standby_archive_delay

#20 Migrate to github actions for tests

Release 1.6.0

standby-clone: Allow cloning of standby server with pg_basebackup

Adds a new primary.pg_basebackup option to the cluster
configuration which if enabled (set to true) will create a
/root/standby-clone-{{ postgres_version }}-{{ postgres_cluster_name }}.sh
script on the standby server which helps to initialise a standby
server.

⚠️ Breaking change: the current role behavior which creates a cloning
script fetching the initial backup from barman will not be
enabled by default anymore. You will need to add the new
primary.restore_barman_directory option in your role
configuration to do so. ⚠️

Recovery: optional restore_command & allow custom command if needed

Adds a new primary.restore_command option which lets you
override the command to use.

⚠️ Breaking change: it renames the existing
primary.restore_directory option to
primary.restore_barman_directory ⚠️ in order to give more context to
this option which will automatically use the barman-wal-restore
script as a restore command.

Finally if none of the two options specified above are specified in
the primary: object then the restore_command is left commented out
in the PG configuration (which is totally fine as it will try to
recover WALs from the primary server directly see
documentation)

tests: remove automatic tests with PG 9.5 & 9.6

parameters: allow wal_level customisation

I allows customisation of the wal_level PG config on all
supported PG versions

tests: running tests on all supported PG versions

core: Add compatibility with PG 12 major version

1.5.0

Release 1.5.0

Allow to use any ansible become method #9

You can now set the following options to use sudo. su method is still used by default.

postgres_become_method: 'sudo'

Allow to set options for barman connectivity #8

Following new options can now be set:

# Barman connectivity
postgres_barman_rsync_options: ''           # Optional
postgres_barman_remote_user: barman         # Optional
postgres_barman_path_prefix: '~'            # Optional, required if using rsync

Allow postgres extensions creation during database creation

The existing "database creation" feature of the role has been extended with "database extension creation" in this new release.

• a new keyword extensions allowing a list of objects of the type { names: List, apt_deps: List } can be specified in the list of databases to be created on a cluster. E.g. of such usage is present in the tests.

Bump minimum ansible version to 2.5

From now on the role will only be available for Ansible 2.5 or later.

Details: This release uses newer loop syntaxes.