Re: BUG #5238: frequent signal 11 segfaults
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #5238: frequent signal 11 segfaults |
| Дата | |
| Msg-id | 25153.1260723491@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: BUG #5238: frequent signal 11 segfaults (Nagy Daniel <nagy.daniel@telekom.hu>) |
| Ответы |
Re: BUG #5238: frequent signal 11 segfaults
|
| Список | pgsql-bugs |
Nagy Daniel <nagy.daniel@telekom.hu> writes:
> I ran "select * from" on both tables. All rows were returned
> successfully, no error logs were produced during the selects.
Well, that would seem to eliminate the initial theory of on-disk
corruption, except that these *other* symptoms that you just mentioned
for the first time look a lot like index corruption. I concur with
Pavel that intermittent hardware problems are looking more and more
likely. Try a memory test first --- a patch of bad RAM could easily
produce symptoms like this.
> Apart from that, I think that pg shouldn't crash in case of
> on-disk corruptions, but log an error message instead.
There is very little that software can do to protect itself from
flaky hardware :-(
regards, tom lane
В списке pgsql-bugs по дате отправления: