3 messages in com.mysql.lists.bugsRe: refreshing mysqld
FromSent OnAttachments
Martin MOKREJŠ22 Nov 2001 02:33 
Michael Widenius22 Nov 2001 04:47 
Sasha Pachev22 Nov 2001 18:17 
Subject:Re: refreshing mysqld
From:Michael Widenius (mon@mysql.com)
Date:11/22/2001 04:47:39 AM
List:com.mysql.lists.bugs

Hi!

"mmokrejs" == mmokrejs <iso-8859-2> writes:

mmokrejs> On Wed, 21 Nov 2001, Sasha Pachev wrote:

On Wednesday 21 November 2001 03:16 am, Martin MOKREJ? wrote:

Hi, ? I've a question: is it expected behaviour that after unpacking a table I have to issue "mysqldmin refresh" to tell mysqld that the table in not readonly anymore and so that it can allow write access to it?

Yes. If you modify the table in any way externally, the correct way to do is is to lock the table (LOCK TABLES), flush it, perform modication, then unlock it ( UNLOCK TABLES). If you do it any other way ( excepting server shutdown, of course), results are unpredicatable.

mmokrejs> Hmm, well I thought myisamchk does these triks itself and that this is
the mmokrejs> difference to old isamchk, which required shutdown of mysqld?

No, myisamchk also requires that you are not using the table. Thats why we have added REPAIR and CHECK as internal commands in MySQL.

Regards, Monty