From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Paul Weaver <pweaver(at)panjiva(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ERROR: could not access status of transaction 283479860 |
Date: | 2015-04-06 18:17:35 |
Message-ID: | 20150406181735.GE4369@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Pweaver (Paul Weaver) wrote:
> We started getting the following error on some transactions on our database
> (when against particular rows run against the table).
>
>
> PGError: ERROR: could not access status of transaction 283479860 DETAIL:
> Could not open file "pg_multixact/members/4D6D": No such file or directory.
>
> We don't know what happen or how to recover. Any advise?
This looks like you overran pg_multixact/members files by wrapping
around the 32 bit counter (NextMultiOffset in your pg_controldata
output); a cleanup process later removed files that were still needed.
This is a Postgres bug, I fear. Recovery is a bit complicated. I see
that your report was made 5 days ago -- have you had any progress on
getting things fixed since then?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Brusselback | 2015-04-06 19:29:07 | Re: pgAgent |
Previous Message | Filipe Pina | 2015-04-06 14:59:59 | Re: Serializable transaction restart/re-execute |