On Sat, May 14, 2016 at 5:38 PM, Venkata Balaji N wrote:
>
> On Wed, May 11, 2016 at 9:04 PM, wrote:
>
>> I apologise for the missing data.
>>
>> we are running 9.1.15 on debian servers.
>>
>
> There is a possibility of making the old master standby if you have
> promoted standby after clean-shu
On Wed, May 11, 2016 at 9:04 PM, wrote:
> I apologise for the missing data.
>
> we are running 9.1.15 on debian servers.
>
There is a possibility of making the old master standby if you have
promoted standby after clean-shutting down the master. I I tested this in
9.2.x and later versions. This
On Wed, May 11, 2016 at 4:35 PM wrote:
> I apologise for the missing data.
>
> we are running 9.1.15 on debian servers.
>
>
I think there was a patch in v9.3 which makes sure that if the master has
been shutdown properly (smart or fast mode), it will ensure that pending
wals are replicated before
I apologise for the missing data.
we are running 9.1.15 on debian servers.
when we promote the old slave, it seems to go fine. Are you saying that it will
cause issues down the line if the previous master is not shut down before
promoting?
I was actually more concerned with the fact that we (s
On Wed, May 11, 2016 at 2:31 PM, wrote:
> Hi All,
>
> we are currently using streaming replication on multiple node pairs. We
> are seeing some issues, but I am mainly interrested in clarification.
>
> When a failover occurs, we touch the trigger file, promoting the previous
> slave to master. Th
Hi All,
we are currently using streaming replication on multiple node pairs. We are
seeing some issues, but I am mainly interrested in clarification.
When a failover occurs, we touch the trigger file, promoting the previous slave
to master. That works perfectly.
For recycling the previous mast
