Thread: PostgreSQL 8.3 data corruption
Hi there,
I have mission-critical data running on PostgreSQL 8.3. My database got corrupted a few days ago as I ran out of disk space.
I had to run pg_resetxlog to get the database started again. I am now experiencing the following errors:
1. ERROR: t_xmin is uncommitted in tuple to be updated
2. ERROR: could not access status of transaction 61323662
Detail: Could not read from file "pg_subtrans/03A7" at offset 188416: No error.
Does anyone know how to resolve the issues above? Would a VACUUM FULL or a dump and restore work? Or is there another way to fix the above.
Thanking you in advance,
Chitra
Hello all,
Any thoughts on this one?
Cheers.
On Tue, May 1, 2012 at 9:51 PM, Chitra Creta <chitracreta@gmail.com> wrote:
Hi there,I have mission-critical data running on PostgreSQL 8.3. My database got corrupted a few days ago as I ran out of disk space.I had to run pg_resetxlog to get the database started again. I am now experiencing the following errors:1. ERROR: t_xmin is uncommitted in tuple to be updated2. ERROR: could not access status of transaction 61323662Detail: Could not read from file "pg_subtrans/03A7" at offset 188416: No error.Does anyone know how to resolve the issues above? Would a VACUUM FULL or a dump and restore work? Or is there another way to fix the above.Thanking you in advance,Chitra
Hello 2012/5/2 Chitra Creta <chitracreta@gmail.com>: > Hello all, > > Any thoughts on this one? > if you can use buckup. If you can't then you have to delete broken rows or broken pages and later rebuild all indexes see http://blog.endpoint.com/2010/06/tracking-down-database-corruption-with.html Regards Pavel Stehule > Cheers. > > > On Tue, May 1, 2012 at 9:51 PM, Chitra Creta <chitracreta@gmail.com> wrote: >> >> Hi there, >> >> I have mission-critical data running on PostgreSQL 8.3. My database got >> corrupted a few days ago as I ran out of disk space. >> >> I had to run pg_resetxlog to get the database started again. I am now >> experiencing the following errors: >> >> 1. ERROR: t_xmin is uncommitted in tuple to be updated >> >> 2. ERROR: could not access status of transaction 61323662 >> Detail: Could not read from file "pg_subtrans/03A7" at offset 188416: No >> error. >> >> Does anyone know how to resolve the issues above? Would a VACUUM FULL or a >> dump and restore work? Or is there another way to fix the above. >> >> >> Thanking you in advance, >> Chitra > >