Re: getting pg_basebackup to use remote destination

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Chuck Martin <clmartin(at)theombudsman(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: getting pg_basebackup to use remote destination
Date: 2018-12-30 20:27:46
Message-ID: CAMkU=1y_+Epa9iyy9VpV1d6VtRv2zKr5Ub_S61Mcs523zpT_3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Dec 29, 2018 at 2:05 PM Chuck Martin <clmartin(at)theombudsman(dot)com>
wrote:

> I thought I knew how to do this, but I apparently don't. I have to set up
> a new server as a standby for a PG 11.1 server. The main server has a lot
> more resources than the standby. What I want to do is run pg_basebackup on
> the main server with the output going to the data directory on the new
> server.
>

pg_basebackup consumes few resources on the standby anyway in the mode you
are running it, other than network and disk. And those are inevitable
given your end goal, so if you could do what you want, I think it still
wouldn't do what you want.

If you really want to spare the network, you can run compression on the
server side then decompress on the standby. Currently you can't compress
on the server when invoking it on the standby, so:

pg_basebackup -D - -Ft -X none |pxz | ssh 10.0.1.16 "tar -xJf - -C
/somewhere/data_test"

Unfortunately you can't use this along with -X stream or -X fetch.

Really I would probably compress to a file and then use scp/rsync, rather
the streaming into ssh. That way if ssh gets interrupted, you don't lose
all the work.

Cheers,

Jeff

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rory Campbell-Lange 2018-12-30 21:31:12 jsonb : find row by array object attribute
Previous Message Francisco Olarte 2018-12-30 19:27:11 Re: getting pg_basebackup to use remote destination