Skip to main content

PgBackMan - Release version 1.2.0

It has been a while since the last release of PgBackMan and with this version we hope to start a new period with more frequent releases. This new release implements some new features and fixes some bugs from version 1.1.0. Source files, RPM and DEB files are available at GitHub.

New features

  • Add support for postgreSQL 9.6

  • Add dbname exception field to register_snapshot_definition

  • Add dbname exception field to register_backup_definitions

  • Possibility of defining multiple snapshots definitions in one command

  • Update show_pgbackman_config to show more information

  • Define a default backup server in all backup servers inputs.

  • Possibility of generating CSV and JSON output with all show_* pgbackman commands

  • Refactor the code used to manage command line parameters and define new parameters.

  • Automatic compression of cluster type backups if gzip is available.

  • New command to move backup definitions between backup servers.

Migration to 1.2.0

It is very important to check the upgrade procedure to version 1.2.0 in the documentation to avoid problems and errors when and after upgrading to the new version.

Check the section "Upgrading PgBackMan" for more information.


  • show_job_queues view does not show the right domain for pgsql_nodes. [Issue:#47]

  • Backup definitions of type CLUSTER getting DELETE status. [Issue:#39]


StevenAnderson (not verified)

Thu, 08/02/2018 - 11:37

Despite the fact that a reinforcement made with PgBackMan can never ensure a full calamity recuperation of all information changed between the minute when the reinforcement was taken and the snapshot of a future crash, they are as yet important in the event that you have to chronicle renditions of a database, move databases between PgSQL nodes and clone databases between creation.

Vanessa Bell (not verified)

Mon, 12/02/2018 - 13:30

Well I was somehow certain with the post its the ideal the feature details and points mentioned above are some points to ponder about, has been the one which has the details mentioned similar to above.

Add new comment

The comment language code.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.