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

From Dmitry Tkach
Subject Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3
Date
Msg-id 3F1825F7.7070301@openratings.com
Whole thread Raw
In response to Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3  (Jeff Eckermann <jeff_eckermann@yahoo.com>)
Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
scott.marlowe wrote:

>>Why doesn't it complain after I restart it then?
>>
>>
>
>Why should it?  If the problem is corrupted data in an index / table
>/system table etc... you won't see an error until it accesses the
>table/index etc... that's causing the problem.
>
>
Right...

So,

1) I do

analyze mytable;

,.. it crashes.

2) I do it again:

analyze mytable;

... it crashes.

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.

So, it looks like, if there is some data structure or a catalog screwed
up, it is not screwed up by 7.2.1 earlier, it is *being* screwed up
somewhere between #3 and #4 above...

Dima


pgsql-general by date:

Previous
From: Yuri Ivanov
Date:
Subject: Re: (Urgent) Regarding double byte support
Next
From: Jonathan Bartlett
Date:
Subject: Re: Is PostgreSQL cluster capable?