Date: Wed, 8 Oct 2014 15:55:38 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: jim_yates <pg@wg5jim.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: could not access status of transaction pg_multixact issue
Message-ID: <20141008185538.GY7043@eldon.alvh.no-ip.org>
References: <1412791213607-5822248.post@n5.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1412791213607-5822248.post@n5.nabble.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

jim_yates wrote:
> I have this issue for 1 table.   Version is 9.3.5  upgraded from 9.2 with
> pg_upgrade a few months ago.
> 
> This issues just started in the last couple of days.
> 
> acustream=# SELECT count(*) from phyorg_charges_to_invoice;
> ERROR:  could not access status of transaction 267035
> DETAIL:  Could not open file "pg_multixact/members/10AD6": No such file or
> directory.
> 
> This error happens when I try and select or vacuum the table.  Inserts still
> work.  I have a hot standby database and I can recover the data from there.  
> Is there any work around for this?  

Please see this thread:
http://www.postgresql.org/message-id/loom.20140930T022539-927@post.gmane.org

My bet is you upgraded to a 9.3 version older than 9.3.5; this means
your relminmxid/datminmxid are set to 1 and need to be updated.

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


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql