Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Date: 2014-02-24 23:20:13
Message-ID: CAM3SWZSmzvLa6FQD6GrQtG=OCQNN2s=Okzr=02oM3z47b0kxig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 24, 2014 at 3:17 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> TBH I don't care about torn pages during normal testing. I don't want to
> suggest disabling it for real workloads with real data, just that it's
> important to do so during development/testing of WAL related code,
> because otherwise it will hide/fixup many errors.

Sure, but you might want to account for torn pages anyway.
Particularly if you're interested in some degree of automation, as we
all seem to be.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-02-24 23:30:25 Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Previous Message Andres Freund 2014-02-24 23:17:40 Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?