| 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 21:21:29 |
| Message-ID: | BA4C09CC-7787-4F42-B91C-876864FB6431@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 18, 2013, at 12:57 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Were there any kind of patterns in the lost data? What kind of workload
> are they running? I have an idea what the issue might be...
On the P1 > S1 case, the data corrupted was data modified in the last few minutes before the switchover. I don't want to over-analyze, but it was within the checkpoint_timeout value for that sever.
On the P2 > S2 case, it's less obvious what the pattern is, since there was no cutover.
Insufficient information on the P3 > S3 case.
Each of them is a reasonably high-volume OLTP-style workload. The P1/P2 client has a very high level of writes; the P3 more read-heavy, but still a fair number of writes.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-18 22:15:59 | Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 |
| Previous Message | Andres Freund | 2013-11-18 20:57:03 | Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 |