Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Tkach <dmitry(at)openratings(dot)com>
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3
Date: 2003-07-18 21:36:42
Message-ID: 5769.1058564202@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dmitry Tkach <dmitry(at)openratings(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luis Magaña 2003-07-18 21:43:00 ODBC query problem AGAIN
Previous Message Tom Lane 2003-07-18 21:28:58 Re: Urgent: 10K or more connections