From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | LEROY TENNISON <leroy_tennison(at)prodigy(dot)net> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: compression in replication |
Date: | 2021-06-17 16:30:48 |
Message-ID: | 20210617163047.GM20766@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Greetings,
We generally prefer to do in-line replies (not top-posting) on these
lists. So, more below.
* LEROY TENNISON (leroy_tennison(at)prodigy(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | still Learner | 2021-06-18 09:02:45 | STDERR not logging after a fix log size |
Previous Message | Vijaykumar Jain | 2021-06-17 14:09:11 | Re: How does vacuum full works if table is partitioned? |