From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | rakeshkumar464 <rakeshkumar464(at)outlook(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup running from a remote machine |
Date: | 2017-11-16 06:47:27 |
Message-ID: | CAMkU=1xcQjg_XWZvk7-0nSUEXakBPdqfoh97ogNeLp0kVc9-GQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 14, 2017 at 8:28 AM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> rakeshkumar464 wrote:
> > If pg_basebackup is run from a remote machine with compress option
> --gzip ,
> > compress level 9,
> > will the compression occur prior to the data being sent on the network or
> > after it has been received
> > at the remote machine.
>
> That only means that the output TAR file will be compressed, it has
> nothing to do with the data transfered from the server.
>
> If you want to compress the data sent over the network, use
> pg_basebackup over an SSL connection with SSL compression enabled.
>
But ssl compression is disabled by default on most systems, and not even
supported at all on many without doing a custom compilation of the ssl
library.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-11-16 07:01:59 | Re: expanded auto and header linestyle double |
Previous Message | Rory Falloon | 2017-11-16 02:36:08 | Re: Setting up replication slave on remote high latency host |