@@ -5,12 +5,16 @@

* Add quiet mode with the commnad line option -q/--quiet. It takes precedence

over verbose mode.

* Compute checksum of global and ACL files

* Add a dump of hba_file and ident_file

* Encrypt and decrypt produced files

* Ensure jobs option is greater than or equal to 1

* Better check and adapt to versions of pg_dump and pg_dumpall

* Upload files to AWS S3

* Upload files to a remote host with SFTP

* Upload files to Google Cloud Storage (GCS)

* Upload files to Azure Blob Storage

* Add a systemd timer for Debian in the package generated by goreleaser

* Check the syntax of the configuration file

## pg_back 2.0.1

@@ -25,7 +25,7 @@ options of the PostgreSQL instance.

* Purge based on age and number of dumps to keep

* Dump from a hot standby by pausing replication replay

* Encrypt and decrypt dumps and other files

* Upload dumps to S3, GCS or a remote host with SFTP

* Upload dumps to S3, GCS, Azure or a remote host with SFTP

## Install

@@ -159,6 +159,11 @@ the `age` tool, independently. Decryption of multiple files can be parallelized

with the `-j` option. Arguments on the commandline (database names when

dumping) are used as shell globs to choose which files to decrypt.

**Please note** that files are written on disk unencrypted in the backup directory,

before encryption and deleted after the encryption operation is complete. This

means that the host running `pg_back` must secure enough to ensure privacy of the

backup directory and connections to PostgreSQL.

### Upload to remote locations

All files produced by a run can be uploaded to a remote location by setting the