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

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>
Subject: Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Date: 2014-02-26 22:22:40
Message-ID: 20140226222240.GD6718@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-02-26 19:03:42 -0300, Alvaro Herrera wrote:
> I forgot to mention that the bug can be reproduced in a hot-standby
> setup with the attached isolation spec. Note that full_page_writes must
> be turned off (otherwise, the updates use full-page writes and then the
> bogus code is not run). Once the spec is executed, in the replica run

Should be "fixable" by just issuing a independent write (another lock,
update) in a previous step...

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-02-26 22:26:46 Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Previous Message Andrew Dunstan 2014-02-26 22:10:42 Re: jsonb and nested hstore