Re: compression in replication - Mailing list pgsql-admin

From Stephen Frost
Subject Re: compression in replication
Date
Msg-id 20210617163047.GM20766@tamriel.snowman.net
Whole thread Raw
In response to Re: compression in replication  (LEROY TENNISON <leroy_tennison@prodigy.net>)
List pgsql-admin
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-transitcompression.  If i remember correctly Postgresql compression must be enabled on both ends.  I had a situation
wherethat 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

Attachment

pgsql-admin by date:

Previous
From: Vijaykumar Jain
Date:
Subject: Re: How does vacuum full works if table is partitioned?
Next
From: still Learner
Date:
Subject: STDERR not logging after a fix log size