Re: PostgreSQL <> MySQL: missing the point?

From: Kaarel <kaarel(at)future(dot)ee>
To: Alexey Borzov <borz_off(at)cs(dot)msu(dot)su>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: PostgreSQL <> MySQL: missing the point?
Date: 2003-09-15 10:17:10
Message-ID: 3F6591A6.5090601@future.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy


> * If MySQL is so stable, why does it have myisamchk utility and
> *built-in* REPAIR TABLE command?

Perhaps this is one of the reasons and it's probably somewhere in the
documentation too so it cannot be a bug therefore it must be a feature :)

Heikki Tuuri "'nosync' is dangerous. If there is a power outage, or the
OS crashes, there is a great chance that your tablespace will be
corrupted. MyISAM always runs in the 'nosync' mode, that is, it never
calls fsync() to flush the files to disk."
http://lists.mysql.com/mysql/148920

Kaarel

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Michael Pohl 2003-09-15 13:47:07 Re: PostgreSQL <> MySQL: missing the point?
Previous Message Alexey Borzov 2003-09-15 09:29:44 PostgreSQL <> MySQL: missing the point?