Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
Date
Msg-id 20150529224829.GC6535@alap3.anarazel.de
Whole thread Raw
In response to Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On 2015-05-30 10:41:01 +1200, Thomas Munro wrote:
> On Sat, May 30, 2015 at 10:29 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> > On Fri, May 29, 2015 at 5:14 PM, Josh Berkus <josh@agliodbs.com> wrote:
> >> Just saw what looks like a report of this issue on 9.2.
> >>
> >> https://github.com/wal-e/wal-e/issues/177
> >
> > Urk.  That looks awfully similar, but I don't think any of the code
> > that is affected here exists in 9.2, or that any of the fixes involved
> > were back-patched to 9.2.  So that might be something else altogether.
> 
> Not only that, the pg_multixact/members *directory* is reported
> missing, which is a different problem entirely.

I don't read that from the log, what does make you think that that's the
case. Afaics it's "just" the 0146 member file that is missing?



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Join Filter vs. Index Cond (performance regression 9.1->9.2+/HEAD)
Next
From: Thomas Munro
Date:
Subject: Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1