From: | Ben Chobot <bench(at)silentmedia(dot)com> |
---|---|
To: | chinnaobi <chinnaobi(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Streaming replication failed to start scenarios |
Date: | 2012-10-23 21:08:10 |
Message-ID: | B017A84A-0438-4E2E-A6FA-5B91B7B70783@silentmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 22, 2012, at 6:57 AM, chinnaobi wrote:
> Hi Laurenz Albe,
>
> I have tested using cygwin rsync in windows 2008 R2, just after restart the
> server.
>
> for 10 GB it took nearly 5 minutes to sync,
> for 50 GB it took nearly 30 minutes, -- too long Though there were no big
> changes.
>
> My requirement is something less than 5 minutes. I am doing high
> availability. In my setup there is WAL archiving enabled as well.
>
> Is there any way I can speedup the configuring dead primary server to
> standby ??
If it's a planned switch, and not a crash, take a look at this thread:
http://archives.postgresql.org/pgsql-general/2012-08/msg00083.php
If it's a crash, then the only way to bring your crashed node back up as a slave to your new master is with another full copy from that master node.
From | Date | Subject | |
---|---|---|---|
Next Message | Xiong He | 2012-10-24 10:09:58 | Re: oracle_fdw with oracle os authentication |
Previous Message | Enke, Dr., Michael | 2012-10-23 20:55:38 | Q: ecpg and UPDATE/DELETE ... RETURNING ... for multiple returned rows |