| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | raokumar(at)netwolves(dot)com |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgre 7.3.2 pg_clog error |
| Date: | 2003-03-21 22:03:52 |
| Message-ID: | 15748.1048284232@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Rao Kumar" <raokumar(at)netwolves(dot)com> writes:
> We are running into a pg_clog problem since we recently upgraded to 7.3.2
> version. The error log reports:
> PANIC: open of /usr/local/pgsql/data/pg_clog/0002 failed: No such file or
> directory
> 2003-03-19 05:46:40 LOG: recycled transaction log file 00000001000000B8
> 2003-03-19 05:51:02 PANIC: open of /usr/local/pgsql/data/pg_clog/0020
> failed: No such file or directory
What are the actual names, mod dates, and sizes of the files in the
pg_clog directory?
The PANICs should produce core dumps --- can you get stack traces from
the crashed backends? (If they don't, fix the postmaster's environment
--- it's probably being started with ulimit -c 0.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Alberto Soto Cordones | 2003-03-21 22:17:36 | CREATE TYPE IN POSTGRES 7.2.3 |
| Previous Message | Robert Treat | 2003-03-21 21:30:36 | Re: Any Monitoring Tools for Postgres? |