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: Josh Berkus <josh(at)agliodbs(dot)com>, 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-19 18:32:10
Message-ID: A19BC379-2AA5-4BC6-8482-C20571D963CD@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Nov 19, 2013, at 10:29 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:

> It's pretty unlikely that any automated testing would have cought this,
> the required conditions are too unlikely for that.

I would expect that "promote secondary while primary is under heavy load" is clear-cut test case. What concerns me more is that we don't seem to have a framework to put in a regression test on the bug you just found (and thank you for finding it so quickly!).

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-11-19 18:34:09 Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1
Previous Message Bruce Momjian 2013-11-19 18:31:55 Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block