Res: Table Locking (Was: Best CPU config for a busy DB server)
- Date: Thu, 15 May 2008 09:30:36 -0700 (PDT)
- From: Wagner Bianchi <wagnerbianchi@xxxxxxxxxxxx>
- Subject: Res: Table Locking (Was: Best CPU config for a busy DB server)
Locking will ocours with MyISAM tables when INSERT, UPDATE, DELETE or REPLACE statemats arrive that tables, lock at the table level. In INNODB engine, a lock ocours at the row-level.
BDB have lock at the page-level.
Wagner Bianchi
Diretor de Tecnologia - INFODBA C&T
wagnerbianchi@xxxxxxxxxxxxxx - (31) 3272 - 0226 / 9114 - 7695
----- Mensagem original ----
De: Rob Wultsch <wultsch@xxxxxxxxx>
Para: JW <jw@xxxxxxxxxx>
Cc: mysql@xxxxxxxxxxxxxxx
Enviadas: Domingo, 11 de Maio de 2008 0:04:17
Assunto: Re: Table Locking (Was: Best CPU config for a busy DB server)
On Sat, May 10, 2008 at 4:24 PM, JW <jw@xxxxxxxxxx> 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@xxxxxxxxx
wultsch (aim)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=wagnerbianchi@xxxxxxxxxxxx
Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/