[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Setting up replication slave on remote high latency host
From:       Rory Falloon <rfalloon () gmail ! com>
Date:       2017-11-16 2:36:08
Message-ID: CANP_6+NaXWNbapLHNZsfPPOgDJ+0h4wdVo67r6fLT0uFW8Fpgg () mail ! gmail ! com
[Download RAW message or body]

Thank you for that. Back to the drawing board!

On Wed, Nov 15, 2017 at 9:30 PM, John R Pierce <pierce@hogranch.com> wrote:

> On 11/15/2017 6:02 PM, Rory Falloon wrote:
>
>>
>> Right now I am trying to dump the database, gzip, move across, and import
>> into the new slave (which is configured as a master to perform the initial
>> setup). Ideally I do this dump, move and import during a period of
>> inactivity on the master so the new server will come up and immediately be
>> able to catch up on replication due to lack of activity. However, I have
>> been importing the current db as a test and after 90 minutes it seems to
>> have only got 2/3 of the way. I am not confident this will work but it
>> seems like the most efficient way to start.
>>
>
>
> you can't use pg_dump to create a slave, as it won't have the same
> timeline.
>
> I would use pg_basebackup, but in general streaming replication over a
> high latency erratic link will never work real well.
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

[Attachment #3 (text/html)]

<div dir="ltr">Thank you for that. Back to the drawing board!</div><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 15, 2017 at 9:30 PM, \
John R Pierce <span dir="ltr">&lt;<a href="mailto:pierce@hogranch.com" \
target="_blank">pierce@hogranch.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 11/15/2017 6:02 PM, Rory Falloon wrote:<br> \
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
Right now I am trying to dump the database, gzip, move across, and import into the \
new slave (which is configured as a master to perform the initial setup). Ideally I \
do this dump, move and import during a period of inactivity on the master so the new \
server will come up and immediately be able to catch up on replication due to lack of \
activity. However, I have been importing the current db as a test and after 90 \
minutes it seems to have only got 2/3 of the way. I am not confident this will work \
but it seems like the most efficient way to start.<br> </blockquote>
<br>
<br></span>
you can&#39;t use pg_dump to create a slave, as it won&#39;t have the same \
timeline.<br> <br>
I would use pg_basebackup, but in general streaming replication over a high latency \
erratic link will never work real well.<span class="HOEnZb"><font \
color="#888888"><br> <br>
<br>
-- <br>
john r pierce, recycling bits in santa cruz<br>
<br>
<br>
<br>
-- <br>
Sent via pgsql-general mailing list (<a href="mailto:pgsql-general@postgresql.org" \
target="_blank">pgsql-general@postgresql.org</a>)<br> To make changes to your \
subscription:<br> <a href="http://www.postgresql.org/mailpref/pgsql-general" \
rel="noreferrer" target="_blank">http://www.postgresql.org/mail<wbr>pref/pgsql-general</a><br>
 </font></span></blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]