"Rao Kumar" <[EMAIL PROTECTED]> 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

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to