pg_basebackup running from a remote machine

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.

Yours,
Laurenz Albe

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Does pg_basebackup on a remote machine follow the standard libpq protocol. I
am not able to force it to use ssl, despite having an entry in pg_hba.conf:

hostnossl all all all reject

From the same remote machine, psql is forced to use ssl.

Makes me wonder whether pg_basebackup has a different protocol.

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Tue, Nov 14, 2017 at 8:28 AM, Laurenz Albe <laurenz.albe@cybertec.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