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

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Dmitry Tkach <dmitry(at)openratings(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: FATAL 2: open of /var/lib/pgsql/data/pg_clog/0EE3
Date: 2003-07-18 15:59:58
Message-ID: Pine.LNX.4.33.0307180955540.1889-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 18 Jul 2003, Dmitry Tkach wrote:

> Hi, everybody!
>
> I was getting these errors (see subject) from time to time on 7.2.1 when
> trying to analyze tables... trying to repeat the statament would usually
> work....
> I then saw somebody else post in the list, mentioning the same problem,
> and Tom Lane's reply to it suggesting to upgrade to 7.2.4, where that
> was supposedly fixed.
>
> I have upgraded recently, and got the same problem again yesterday... It
> seems to have become even worse, as it was happenning consistently, even
> when I tried to repeat the query (with 7.2.1, the second time always
> used to work, as far as I remember)... it seems to have went away after
> I have restarted the server manually...
>
> Was I wrong deducing the assumption that it should be fixed in 7.2.4
> from that Tom's message?
> Or is this news to you guys too?
>
> Any idea what is causing this, and/or how it can be avoided?

did you dump and reload your database? It may well be that 7.2.1 planted
logic bombs in the base directory that 7.2.4 can't fix now. I.e. some
data structure got munged and now 7.2.4 is busy complaining about it.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Doug McNaught 2003-07-18 16:02:53 Re: Scheduled back up (fwd)
Previous Message scott.marlowe 2003-07-18 15:53:28 Re: Urgent: 10K or more connections