| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Matthias(dot)Pitzl(at)izb(dot)de |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strange database corruption with PostgreSQL 7.4.x on |
| Date: | 2006-09-20 12:55:40 |
| Message-ID: | 1158756940.10595.1.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2006-09-20 at 14:34 +0200, Matthias(dot)Pitzl(at)izb(dot)de wrote:
> Hello!
>
> We're running the latest release of PostgreSQL 7.4.13 on a Debian Sarge
> machine. Postgres has been compiled by oureselves.
> We have a pretty big database running on this machine, it has about 6.4 GB
> approximately. One table contains about 55 million rows.
> Into this table we insert about 500000 rows each day. Our problem is that
> without any obvious reason the database gets corrupt. The messages we get
> are:
> invalid page header in block 437702 of relation "xxxx"
> We already have tried out some other versions of 7.4. On another machine
> running Debian Woody with PotgreSQL 7.4.10 we don't have any problems.
> Kernels are 2.4.33 on the Sarge machine, 2.4.28 on the Woody machine. Both
> are SMP kernels.
> Does anyone of you perhaps have some hints what's going wrong here?
Most likely causes in these cases tends to be, bad memory, bad hard
drive, bad cpu, bad RAID / IDE / SCSI controller, loss of power when
writing to IDE drives / RAID controllers with cache with no battery
backup.
I.e. check your hardware.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AgentM | 2006-09-20 13:05:00 | Re: postgresql rising |
| Previous Message | Matthias.Pitzl | 2006-09-20 12:34:34 | Strange database corruption with PostgreSQL 7.4.x on Debian Sarge |