Pitrery 3.4

WARNING: PITRERY IS NOW DEPRECATED

• Support Postgres 14.
• Packages for CentOS 8, Debian buster and bullseye.
• Allow to customize recovery_end_commend.
• Fix rsync options protection.

Pitrery 3.3

• [Bugfix] pitrery restore: could not get the ending timestamp

Pitrery 3.2

• Pitrery version 3.2 is compatible with PostgreSQL version 13.
• Add CI for local tests (see CONTRIBUTING.md).
• Abort check if backup_timestamp is not available (#130)

Pitrery 3.1

• Correct *_xlog to *_wal symbolic link
• protect qw with double comma - apply qw update to archive_wal and restore_wal

Pitrery 2.5

• purge is now working for bash before 4.2 (was broken in pitrery 2.4)
• Improve check for uncompress WAL

Version 3.0

Pitrery version 3.0 is compatible with PostgreSQL version 12.

PostgreSQL in this version has changed how recovery configuration is managed.

• There is be no more "recovery.conf" file:
  • The recovery configuration keys are read from the postgresql.conf file.
    Upon restoration, recovery.conf settings are written by pitrery at the end of the postgresql.conf file.
  • A "recovery.signal" or "standby.signal" will be used by the restored cluster to know what action to take
    A new option is declared: RESTORE_MODE (or the "-m" switch). For restoration, it must be set either to "recovery" or "standby".
• Multiple conflicting recovery_target* specifications are not allowed. PostgreSQL will make the check on startup.
• We now advance to the latest timeline by default.

Since PostgreSQL version 10, "xlog" has been renamed to "wal". Make this change in pitrery:

• "archive_xlog" script is renamed to "archive_wal"
• "restore_xlog" script is renamed to "restore_wal"
• configuration key PGXLOG is renamed to PGWAL
• the WAL archive directory ARCHIVE_DIR is set by default to "$BACKUP_DIR/archived_wal"

Pitrery 2.4

• Warn about untested PostgreSQL version on restore.
• Few updates in collaborative tooling.

Pitrery 2.2

v2.2

Release version 2.2