From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, alvherre(at)atentus(dot)com, pgsql-general(at)postgresql(dot)org, vmikheev(at)SECTORBASE(dot)COM |
Subject: | Re: Database corruption? |
Date: | 2001-10-31 01:30:28 |
Message-ID: | 200110310130.f9V1USC02306@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2001-10-31 01:34:07 | Re: Database corruption? |
Previous Message | Alvaro Herrera | 2001-10-31 01:20:31 | Re: Database corruption? |