From: LEROY TENNISON <leroy_tennison@prodigy.net>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: compression in replication
Date: Wed, 16 Jun 2021 19:21:40 +0000 (UTC)
Message-ID: <192101066.1663055.1623871300493@mail.yahoo.com> (raw)
In-Reply-To: <CAM+6J963wj42DkBYb-ADdeAWuEUXO3eo1FeVge5N=Z8rM7h+rw@mail.gmail.com>
References: <1ltQeA-000URA-EE@unimaticaspa.it>
<CAM+6J97VdKJjaU2Uwn_GYThy23q0-29c2hjRrbZZh3_8eO-oJA@mail.gmail.com>
<CAM+6J963wj42DkBYb-ADdeAWuEUXO3eo1FeVge5N=Z8rM7h+rw@mail.gmail.com>
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@gmail.com> 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."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: leroy_tennison@prodigy.net
Subject: Re: compression in replication
In-Reply-To: <192101066.1663055.1623871300493@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox