Re: Integrity on large sites

From: "Alexander Staubo" <alex(at)purefiction(dot)net>
To: PFC <lists(at)peufeu(dot)com>
Cc: "Scott Ribe" <scott_ribe(at)killerbytes(dot)com>, "Naz Gassiep" <naz(at)mira(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Integrity on large sites
Date: 2007-05-23 21:46:08
Message-ID: 88daf38c0705231446t469ace4dj84fbd59080e397a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/23/07, PFC <lists(at)peufeu(dot)com> wrote:
> +-------------------+-------+----------+-----------------------------+
> | Table | Op | Msg_type | Msg_text |
> +-------------------+-------+----------+-----------------------------+
> | forum_bench.posts | check | warning | Table is marked as crashed |
> | forum_bench.posts | check | error | Found 588137 keys of 588135 |
> | forum_bench.posts | check | error | Corrupt |
> +-------------------+-------+----------+-----------------------------+

I find it hard to believe that this is MySQL's fault and not some
problem with your setup. Granted, MySQL is a pretty bad database, but
it's not *that* bad -- your example implies that heavily MyISAM-based
(you don't say whether this is MyISAM or InnoDB) sites such as
Slashdot and Flickr should be falling over every hour.

Alexander.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2007-05-23 21:49:16 Re: the future of pljava development
Previous Message Ron Johnson 2007-05-23 21:31:50 Re: Integrity on large sites