Re: 9.3.9 and pg_multixact corruption - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: 9.3.9 and pg_multixact corruption
Date
Msg-id 20150910224546.GV2912@alvherre.pgsql
Whole thread Raw
In response to 9.3.9 and pg_multixact corruption  (Bernd Helmle <bernd@oopsware.de>)
Responses Re: 9.3.9 and pg_multixact corruption  (Thomas Munro <thomas.munro@enterprisedb.com>)
Re: 9.3.9 and pg_multixact corruption  (Bernd Helmle <bernd@oopsware.de>)
List pgsql-hackers
Bernd Helmle wrote:
> A customer had a severe issue with a PostgreSQL 9.3.9/sparc64/Solaris 11
> instance.
> 
> The database crashed with the following log messages:
> 
> 2015-09-08 00:49:16 CEST [2912] PANIC:  could not access status of
> transaction 1068235595
> 2015-09-08 00:49:16 CEST [2912] DETAIL:  Could not open file
> "pg_multixact/members/FFFF5FC4": No such file or directory.
> 2015-09-08 00:49:16 CEST [2912] STATEMENT:  delete from StockTransfer
> where oid = $1 and tanum = $2 

I wonder if these bogus page and offset numbers are just
SlruReportIOError being confused because pg_multixact/members is so
weird (I don't think it should be the case, since this stuff is using
page numbers only, not anything related to how each page is layed out).

Anyway, can you please request pg_controldata to be run on the failed
cluster and paste it here?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: 9.3.9 and pg_multixact corruption
Next
From: Thomas Munro
Date:
Subject: Re: 9.3.9 and pg_multixact corruption