From: Stephen Frost <sfrost@snowman.net>
To: LEROY TENNISON <leroy_tennison@prodigy.net>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: compression in replication
Date: Thu, 17 Jun 2021 12:30:48 -0400
Message-ID: <20210617163047.GM20766@tamriel.snowman.net> (raw)
In-Reply-To: <192101066.1663055.1623871300493@mail.yahoo.com>
References: <1ltQeA-000URA-EE@unimaticaspa.it>
<CAM+6J97VdKJjaU2Uwn_GYThy23q0-29c2hjRrbZZh3_8eO-oJA@mail.gmail.com>
<CAM+6J963wj42DkBYb-ADdeAWuEUXO3eo1FeVge5N=Z8rM7h+rw@mail.gmail.com>
<192101066.1663055.1623871300493@mail.yahoo.com>
Greetings,
We generally prefer to do in-line replies (not top-posting) on these
lists. So, more below.
* LEROY TENNISON (leroy_tennison@prodigy.net) wrote:
> 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.
In general, rsync, sftp, and scp are very poor choices for archive
command as they don't do anything to ensure that the WAL is actually
written out to disk and also don't do a variety of other sensible checks
to make sure the WAL matches the PG database, there's a history file for
the timeline the WAL is on, etc.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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: sfrost@snowman.net, leroy_tennison@prodigy.net
Subject: Re: compression in replication
In-Reply-To: <20210617163047.GM20766@tamriel.snowman.net>
* 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