Keep in mind that this can be accomplished in other ways depending on what archive_command you're using. rsync, and sftp (I don't recommend scp due to security concerns but it does compression as well) both have parameters to do in-transit compression. If i remember correctly Postgresql compression must be enabled on both ends. I had a situation where that wasn't easy to do and opted for external (to Postgresql) compression.
On Wednesday, June 16, 2021, 2:56:09 PM UTC, Vijaykumar Jain <vijaykumarjain.github@xxxxxxxxx> wrote:
sorry, the link was broken.
this was the param.
"wal_compression (boolean)
When this parameter is on, the PostgreSQL server compresses a full
page image written to WAL when full_page_writes is on or during a base
backup. A compressed page image will be decompressed during WAL
replay. The default value is off. Only superusers can change this
setting.
Turning this parameter on can reduce the WAL volume without increasing
the risk of unrecoverable data corruption, but at the cost of some
extra CPU spent on the compression during WAL logging and on the
decompression during WAL replay."
this was the param.
"wal_compression (boolean)
When this parameter is on, the PostgreSQL server compresses a full
page image written to WAL when full_page_writes is on or during a base
backup. A compressed page image will be decompressed during WAL
replay. The default value is off. Only superusers can change this
setting.
Turning this parameter on can reduce the WAL volume without increasing
the risk of unrecoverable data corruption, but at the cost of some
extra CPU spent on the compression during WAL logging and on the
decompression during WAL replay."
