Re: 9.3.9 and pg_multixact corruption

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Bernd Helmle <bernd(at)oopsware(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 9.3.9 and pg_multixact corruption
Date: 2015-09-10 22:45:46
Message-ID: 20150910224546.GV2912@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Костя Кузнецов 2015-09-10 22:52:30 New gist vacuum.
Previous Message Alvaro Herrera 2015-09-10 22:35:34 Re: 9.3.9 and pg_multixact corruption