| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Rob Wultsch | Date: | May 11 2008 5:04am |
| Subject: | Re: Table Locking (Was: Best CPU config for a busy DB server) | ||
| View as plain text | |||
On Sat, May 10, 2008 at 4:24 PM, JW <jw@stripped> wrote: >> Table locking will occur with MyISAM tables when any row(s) of the table is >> being updated (Update,Delete,Insert,Load Data etc). >> If you are only executing Select statements, then they can be executed in >> parallel and won't be blocked. > > > Just curious: you say "with MyISAM tables" - do any of the other table types > (InnoDB, Falcon, etc) behave differently? > > Thanks, > > JW "When locks are necessary, InnoDB uses row-level locking." MySQL 5.0 Certification Study Guide, page 419 -- Rob Wultsch wultsch@stripped wultsch (aim)
| Thread | ||
|---|---|---|
| • Best CPU config for a busy DB server | JW | 9 May 2008 |
| • Re: Best CPU config for a busy DB server | Saravanan | 9 May 2008 |
| • Re: Table Locking (Was: Best CPU config for a busy DB server) | JW | 10 May 2008 |
| • Re: Table Locking (Was: Best CPU config for a busy DB server) | mos | 10 May 2008 |
| • Re: Table Locking (Was: Best CPU config for a busy DB server) | JW | 11 May 2008 |
| • Re: Table Locking (Was: Best CPU config for a busy DB server) | Rob Wultsch | 11 May 2008 |
