Re: pg_basebackup on slave running for a long time - Mailing list pgsql-general

From John R Pierce
Subject Re: pg_basebackup on slave running for a long time
Date
Msg-id ab47b6d5-d5e3-869b-c718-cd47a1e9010d@hogranch.com
Whole thread Raw
In response to pg_basebackup on slave running for a long time  (Subhankar Chattopadhyay <subho.atg@gmail.com>)
Responses Re: pg_basebackup on slave running for a long time  (Subhankar Chattopadhyay <subho.atg@gmail.com>)
List pgsql-general
On 11/20/2016 9:29 PM, Subhankar Chattopadhyay wrote:
> We have setup PostgreSQL master-slave topology with Streaming
> replication setup.
> One of the steps for setting up streaming replication is to do
> pg_basebackup on slave from master.
>
> For subsequent update of this database, this step is repeated every
> time, deleting the existing data copy of slave and running
> pg_basebackup again.
>
> For a huge data size of over 500GB, it takes  a lot of time to copy
> the data from master to slave.
> We were looking for some optimization technique so that it doesnt have
> to copy the whole data in every update of the system.
>
> Is there a way to do that? Can somebody throw some light on this?

if you have streaming replication, why do you delete it and start over ??!?

the streaming replication should replicate all updates of the master in
near realtime to the slave(s).


--
john r pierce, recycling bits in santa cruz



pgsql-general by date:

Previous
From: Subhankar Chattopadhyay
Date:
Subject: pg_basebackup on slave running for a long time
Next
From: Subhankar Chattopadhyay
Date:
Subject: Re: pg_basebackup on slave running for a long time