Nagy Daniel <nagy(dot)daniel(at)telekom(dot)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
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2009-12-13 18:06:34|
|Subject: Re: BUG #5240: Stable Functions that return a table type with a dropped column fail |
|Previous:||From: Pavel Stehule||Date: 2009-12-13 16:13:30|
|Subject: Re: BUG #5238: frequent signal 11 segfaults|