| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(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:29:31 |
| Message-ID: | 20131119182931.GC7240@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-11-19 10:27:30 -0800, Christophe Pettus wrote:
>
> On Nov 19, 2013, at 10:25 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > I am not sure how much code it's going to take (I'd hope somewhat less),
> > but it certainly will take some time to agree how it should be built and
> > then building and integrating it.
>
> Given that the situation we're in right now is that we have an unknown
> number of silently corrupt secondaries out there which will only be
> discovered when someone promotes them to being a primary (possibly
> because the current primary died without a backup), I'd say that this
> is something pretty urgent.
It's pretty unlikely that any automated testing would have cought this,
the required conditions are too unlikely for that.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-19 18:31:55 | Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |
| Previous Message | Christophe Pettus | 2013-11-19 18:27:30 | Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 |