>
>>> Some poking through the source code finds only one match for that error
>>> message, which is in relcache.c. It looks like you have a row in
>>> pg_attribute that claims to belong to that relation, but has attnum
>>> 32533. It would be interesting to see the results for
>>> select * from pg_attribute where attrelid = 'largedata'::regclass
>>
>> [see attached]
>Hmm, no sign of any such row here ... try reindexing pg_attribute.
It gets more interesting:
MCS=# reindex table pg_attribute;
ERROR: could not access status of transaction 276828288
DETAIL: Could not open file "pg_subtrans/1080": No such file or directory.
Couldn't force the reindex, and vacuuming didn't help. I've checked the
directory and there's only one file in it ('0004').
There's lots of previous info about that error, not none that I've found (yet)
that have the same detail description (it usually says 'Invalid argument'
instead). At this point this looks pretty serious, and unless there's a
specific way to deal with this error (without hopefully running into other new
ones), I might just go with our plan to recover the data using the backup,
instead of spending more time on a possibly lost cause.
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
