List: | General Discussion | « Previous MessageNext Message » | |
From: | Michael Widenius | Date: | June 19 2001 11:56am |
Subject: | RE: MySQL 3.23.39 released | ||
View as plain text |
hi! >>>>> "Steven" == Steven Roussey <sroussey@stripped> writes: Steven> Now I have a question: Does this also apply to automatic >> repair inside Steven> mysqld? I'd finally use the feature if its true... >> >> >> If you just run CHECK TABLE, it will repair the open count (it should >> always have done that). >> >> myisamchk --fast --force is equal to: >> >> run CHECK TABLE on all tables >> Run REPAIR TABLE on tables which was not marked as ok. Steven> I was refering to --myisam-recover=FORCE Steven> As I remember, it would repair tables that had a open count > 0 (at least Steven> back when I first tried using it). I checked this and at least now it only repairs the table if a check table finds something wrong. Regards, Monty
Thread | ||
---|---|---|
• Some questions/concerns about MySQL | Eric Maryniak | 12 Mar |
• Re: Some questions/concerns about MySQL | Sasha Pachev | 12 Mar |
• Re: Some questions/concerns about MySQL | Christian Mack | 13 Mar |
• Re: Some questions/concerns about MySQL | Thimble Smith | 13 Mar |
• Re: Some questions/concerns about MySQL | Ed Carp | 13 Mar |
• Re: MySQL 3.23.39 released | Steven Roussey | 15 Jun |
• Re: MySQL 3.23.39 released | Michael Widenius | 15 Jun |
• RE: MySQL 3.23.39 released | Steven Roussey | 19 Jun |
• RE: MySQL 3.23.39 released | Michael Widenius | 19 Jun |
• mysqld 3.23.36 -- new connections get stuck in "Open Tables" | Jamie Mason | 18 Jun |