Re: Streaming replication failed to start scenarios

From: chinnaobi <chinnaobi(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Streaming replication failed to start scenarios
Date: 2012-10-17 09:21:25
Message-ID: 1350465685820-5728557.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hey Laurenz Albe,

Thank you for the quick reply..

> 3. When the dead primary is switchedto standby the streaming is not
> happening due to current_wal_location is ahead in the standby server
is
> ahead of wal_sent_location. In this case how can I start streaming
without
> taking a fresh base backup from current primary ??

>>The parenthesis in your previous question and this question suggest
>>that you missed out on one thing:

>>When the standby is promoted, it starts a new time line, so it
>>is on a different time line from the old master. The old
>>primary cannot be turned to a standby without a new base backup
>>(possibly via rsync to speed up things).

>>This time line switch is a mechanism that prevents precisely
>>the problems you are anticipating.

But taking 200 GB to 500 GB DB base backup is impossible for me. Is there
any other solution ??

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Streaming-replication-failed-to-start-scenarios-tp5728519p5728557.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message chinnaobi 2012-10-17 09:38:51 Re: How to avoid base backup in automated failover
Previous Message Albe Laurenz 2012-10-17 08:16:31 Re: 9.1/9.2 SERIALIZABLE: expected serialization failure between INSERT and SELECT not encountered