could not access status of transaction pg_multixact issue

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?  


From pg_class       table_name         |   relfrozenxid    
---------------------------+----------phyorg_charges_to_invoice | 84645615
(1 row)

acustream=# SELECT datname, age(datfrozenxid) FROM pg_database;  datname    |   age    
--------------+----------acustream    | 84652806

pg_controldata:

pg_control version number:            937
Catalog version number:               201306121
Database system identifier:           6006392596691943358
Database cluster state:               in production
pg_control last modified:             Wed 08 Oct 2014 11:48:43 AM MDT
Latest checkpoint location:           342/B225BBF8
Prior checkpoint location:            342/59915308
Latest checkpoint's REDO location:    342/8B0AF830
Latest checkpoint's REDO WAL file:    00000001000003420000008B
Latest checkpoint's TimeLineID:       1
Latest checkpoint's PrevTimeLineID:   1
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID:          0/84922090
Latest checkpoint's NextOID:          274840
Latest checkpoint's NextMultiXactId:  302394
Latest checkpoint's NextMultiOffset:  2391258
Latest checkpoint's oldestXID:        1799
Latest checkpoint's oldestXID's DB:   1
Latest checkpoint's oldestActiveXID:  84654342
Latest checkpoint's oldestMultiXid:   1
Latest checkpoint's oldestMulti's DB: 1
Time of latest checkpoint:            Wed 08 Oct 2014 11:47:51 AM MDT
Fake LSN counter for unlogged rels:   0/1
Minimum recovery ending location:     0/0
Min recovery ending loc's timeline:   0
Backup start location:                0/0
Backup end location:                  0/0
End-of-backup record required:        no
Current wal_level setting:            hot_standby
Current max_connections setting:      200
Current max_prepared_xacts setting:   0
Current max_locks_per_xact setting:   64
Maximum data alignment:               8
Database block size:                  8192
Blocks per segment of large relation: 131072
WAL block size:                       8192
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Maximum size of a TOAST chunk:        1996
Date/time type storage:               64-bit integers
Float4 argument passing:              by value
Float8 argument passing:              by value
Data page checksum version:           0
ls -l pg_multixact/offsets
total 1204
-rw-------. 1 postgres postgres 262144 May 29 23:41 0000
-rw-------. 1 postgres postgres 262144 May 31 01:28 0001
-rw-------. 1 postgres postgres 262144 Aug  8 09:58 0002
-rw-------. 1 postgres postgres 262144 Sep 30 16:35 0003
-rw-------. 1 postgres postgres 163840 Oct  8 11:31 0004



--
View this message in context:
http://postgresql.1045698.n5.nabble.com/could-not-access-status-of-transaction-pg-multixact-issue-tp5822248.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.