OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Res: Table Locking (Was: Best CPU config for a busy DB server)

From: Wagner Bianchi (wagnerbianchiyahoo.com.br)
Date: Thu May 15 2008 - 11:30:36 CDT


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 wagnerbianchiinfodba.com.br - (31) 3272 - 0226 / 9114 - 7695 ----- Mensagem original ---- De: Rob Wultsch <wultschgmail.com> Para: JW <jwmailsw.com> Cc: mysqllists.mysql.com 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 <jwmailsw.com> 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 wultschgmail.com wultsch (aim) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=wagnerbianchiyahoo.com.br Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento! http://br.mail.yahoo.com/