| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(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 16:53:11 |
| Message-ID: | 3F1825F7.7070301@openratings.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Bartlett | 2003-07-18 17:04:55 | Re: Is PostgreSQL cluster capable? |
| Previous Message | Yuri Ivanov | 2003-07-18 16:50:01 | Re: (Urgent) Regarding double byte support |