GitLab

Additional fixes for yum repo changes upstream

Properly handle WAL directory in backup scripts for version >=10

Check pgdg repository package task for RHEL based distros should check pgdg-redhat-repo package

As of 15 April 2019, there is only one repository RPM per distro, and it includes repository information for all available PostgreSQL releases.

declarations

replaced deprecated include with include_tasks

ordering. Supercedes #13.

Move hardcoded value 'postgres' into variable 'postgresql_user_name'

Rationale: provides mechanism for overriding PostgreSQL system user.
In particular, this may be needed when used together with
[ansible-galaxy-os](https://github.com/galaxyproject/ansible-galaxy-os)
role, which provides that option (variable: postgres_user_name).

(Assumption: postgresql user name and group name are the same.)

Update syntax, remove deprecation warnings

1) Do not use filter syntax for tests
2) Do not use Jinja2 syntax in when clause

Fix pgdg package name for 8.4

Fix config for PostgreSQL < 9.3

Fix default ~postgres/backup for local backups

The package names for PostgreSQL 8.4 follow a slightly different naming
pattern. Fixed the matching logic in get_repo_rpm_release.py.

Also changed the script to output the whole package name, which is then
used in the install task. This is to prevent having to fiddle with jinja
filters in the install task to get the correct download url.

the include_dir option was added in version 9.3 [1], directly include
the ansible-generated config file for earlier versions

[1] https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.3#Configuration_directive_.27include_dir.27

The problem was that scripts ended up quoting the value
like this
mutex="~postgres/backup/walmutex"
and ~postgres did not get expanded correctly.

this is normal and ok.

I swear I write better shell than this these days.