> I have been troubled by a really strange problem. Populating with huge
> data (~7GB) cause random failures, for example a misterious unique
> constaraint violation, count(*) shows incorrect number, pg_temp*
> suddenly disappear (the table in question is a temporary table). These
> are really hard to reproduce and happen on 7.0 to current, virtually
> any PostgreSQL releases. Even on an identical system, the problems are
> sometimes gone after re-initdb...
>
> I now suspect that some hardware failures might be the source of the
> trouble. Problem is, I see no sign so far from the standard system
> logs, such as syslog or messages.
>
> It would be really nice if PostgreSQL could be protected from such
> hardware failures using CRC or whatever...
At a minimum, for cases where hardware problems are suspected, we should
have some CRC detection code we can turn on.
Tatsuo, does --enable-cassert help?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
