| From: | "Paul McGarry" <paul(at)paulmcgarry(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Best way to fix Error: could not access status of transaction? |
| Date: | 2008-01-08 06:48:46 |
| Message-ID: | a056b1d40801072248x1b6483b9j68c3c0f03df2f26c@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rihad | 2008-01-08 06:50:18 | need to dump/restore data for 8.3beta2 -> 8.3RC1 upgrade? |
| Previous Message | Devrim GÜNDÜZ | 2008-01-08 06:20:19 | Re: Announcing PostgreSQL RPM Buildfarm |