| From: | "Chris Hoover" <revoohc(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | 8.1.3 Problem |
| Date: | 2007-01-31 21:08:06 |
| Message-ID: | 1d219a6f0701311308n3c90bd1i1b7168b055f506d5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I am starting to have some significant problems with one of my
8.1.3databases. I am getting more and more of these errors:
wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,16,2007-01-31
15:31:48 EST,342126177,UPDATE,ERROR: could not access status of transaction
253762136
wbd,20552,dholton,2007-01-31 15:32:27.137 EST,45c0fcb4.5048,17,2007-01-31
15:31:48 EST,342126177,UPDATE,DETAIL: could not open file "pg_clog/00F2":
No such file or directory
This is happening more and more, and on seeming random databases. Any idea
what is going on? I have already dumped and reloaded 2-3 of my databases
and now have about 3 more suffering from this.
Right now, I can't upgrade to 8.1.6 until around March (have to wait until
the current release of our application is released). I have 7 databases
running 8.1.3 (6 prod and 1 test/dev) and only the test/dev is exhibiting
this problem
Any help/ideas on what is going on and how to fix would be appreciated.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Holdoway | 2007-01-31 21:46:06 | blobs |
| Previous Message | Peter Koczan | 2007-01-31 18:23:05 | Re: pg_dumpall problems |