This is a discussion on Best way to fix Error: could not access status of transaction? within the Pgsql General forums, part of the PostgreSQL category; --> Hi, I have a database (8.1.10 via Ubuntu) that has started reporting: <2008-01-08 08:51:14 EST|>ERROR: could not access status ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I have a database (8.1.10 via Ubuntu) that has started reporting: <2008-01-08 08:51:14 EST|>ERROR: could not access status of transaction 707406378 <2008-01-08 08:51:14 EST|>DETAIL: could not open file "pg_clog/02A2": No such file or directory when trying to do an autovacuum. By vacuuming tables individually I have determined that the problem occurs in a table that doesn't contain critical data (basically log information that is kept for a month in case it is useful). Posts I have found in the archive seem to advocate manually trying to create the missing pg_clog file however I would prefer not to fiddle with it manually if there is another way to clear the error. Bearing in mind that I don't particularly need the data in that table can I simply truncate it or drop/recreate it to clear the above error? Paul ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
| ||||
| Paul McGarry wrote: > Bearing in mind that I don't particularly need the data in that table > can I simply truncate it or drop/recreate it to clear the above error? Yes, truncate should work. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |