Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3 - Mailing list pgsql-general

From Tom Lane
Subject Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3
Date
Msg-id 5769.1058564202@sss.pgh.pa.us
Whole thread Raw
In response to Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3  (Dmitry Tkach <dmitry@openratings.com>)
Responses Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3  (Dmitry Tkach <dmitry@openratings.com>)
List pgsql-general
Dmitry Tkach <dmitry@openratings.com> writes:
> 3) I restart the server manually, and try again
> analyze mytable;
> ... it *works*

> 4) I let it run for a while, then try again:
> analyze mytable;
> ... it crashes.

Proves nothing, since ANALYZE only touches a random sample of the rows.

If you get that behavior with VACUUM, or a full-table SELECT (say,
"SELECT count(*) FROM foo"), then it'd be interesting.

What range of file names do you actually have in pg_clog/, anyway?

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Urgent: 10K or more connections
Next
From: Luis Magaña
Date:
Subject: ODBC query problem AGAIN