Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1
Date: 2013-11-18 19:58:23
Message-ID: 79C8DBD3-2BA8-4C30-8DCE-5A6321C4985F@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Nov 18, 2013, at 11:47 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:

> Did you have hot_standby enabled on all of those machines? Even on the
> 9.0.13 cluster?

Actually, it's a bit more complex than this:

1. We don't know about P0, the 9.0.13 machine. I assume it was, but it was managed elsewhere.
2. P1 never had hot_standby = 'on', as it was never intended to be a hot stand_by.
3. S1 did have hot_standby = 'on.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2013-11-18 20:00:55 Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1
Previous Message Christophe Pettus 2013-11-18 19:55:10 Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1