I've seen this happen before. Try and do a pg_dump first, then try
'pg_resetxlog', and if that doesn't work, clear out the database
completely and restore the dump. (Be careful you have that dump backed
up in a safe place!)
Rob
> -----Original Message-----
> From:
dspace-t...@lists.sourceforge.net
> [mailto:
dspace-t...@lists.sourceforge.net] On Behalf Of
> Andrew Wang
> Sent: 06 October 2005 11:15
> To:
dspac...@lists.sourceforge.net
> Subject: [Dspace-tech] PostgreSQL database corruption
>
> Hello,
>
> Our postgresql database (version 7.4.3) seems corrupted
> (not sure why
> yet). Running vacuumdb command gives the following error:
>
> dspace/pgsql/bin/vacuumdb --analyze dspace 2>&1
> vacuumdb: vacuuming of database "dspace" failed: ERROR:
> could not access status of transaction 1667768432
> DETAIL: could not read from file
> "/dspace/pgsql/data/pg_clog/0636" at offset 131072: Success
>
>
> Also in dspace.log, exceptions are everywhere
>
> org.postgresql.util.PSQLException: ERROR: could not access
> status of transaction 544108402
>
> at
> org.postgresql.util.PSQLException.parseServerError(PSQLExcepti
> on.java:139)
>
>
> Does anybody know what is the best way to solve this problem?
>
> Thanks.
>
> Andrew
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
> discussions,
> and more.
http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> DSpace-tech mailing list
>
DSpac...@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
>