Re: innodb select

Hello. > Does this have anything to do with the variable: > > | tx_isolation| REPEATABLE-READ| It seems it is. If you use InnoDB only due to speed issues, change the transaction isolating level to READ UNCOMMITED. See: http://dev.mysql.com/doc/refman/5.0/e

innodb select

Hi All, I just had a question on selects on a innodb table. Looking on google, I find that there are different types of selects: select IN SHARE MODE and FOR UPDATE I am administering a database with a fairly large innodb table. I am running into problems with one of my users insisting o

Re: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

Janusz Krzysztofik wrote: > ... > I am trying to optimize MySQL (3.23.49 from Debian stable) setup for > ASPseek application. I decided to try InnoDB in order to be able > to update tables while performing time consuming selects. > After converting all tables to InnoDB I noticed a big difference >

Re: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

Hi, > > > You are not using any indicies, because there aren't any that could be > > > used in this query. > > > Try adding an index on (status,deleted) > > > > I wonder: how many possible different values would such an index > > return? > > mysql> select distinct status, deleted from urlword; > +

Re: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

Martijn Tonies wrote: > > Hi, > > > You are not using any indicies, because there aren't any that could be > > used in this query. > > Try adding an index on (status,deleted) > > I wonder: how many possible different values would such an index > return? mysql> select distinct status, deleted fr

Re: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

Hi, > You are not using any indicies, because there aren't any that could be > used in this query. > Try adding an index on (status,deleted) I wonder: how many possible different values would such an index return? If this is a (very) low value, won't the index make things slower (if it's being u

RE: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

ndex (was: Big difference in MyISAM and InnoDB SELECT speed) Marc, Thank you for your prompt answer. I run EXPLAIN in both cases and got: MyISAM (fast): mysql> explain select url_id from urlword where deleted=0 and status

Re: Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

De : Janusz Krzysztofik [mailto:[EMAIL PROTECTED] Envoyé : lundi 24 novembre 2003 13:58 A : [EMAIL PROTECTED] Objet : Big difference in MyISAM and InnoDB SELECT speed Hello, I am trying to optimize MySQL (3.23.49 from Debian stable) setup for ASPseek application. I decided to try InnoDB in order to

Inefficient use of index (was: Big difference in MyISAM and InnoDB SELECT speed)

evant one). > > Have you done an EXPLAIN on your query ? > > May be an index on (origin,status,deleted) could help. > > Marc. > > -Message d'origine- > De : Janusz Krzysztofik [mailto:[EMAIL PROTECTED] > Envoyé : lundi 24 novembre 2003 13:58 > A : [E

RE: Big difference in MyISAM and InnoDB SELECT speed

nvoyé : lundi 24 novembre 2003 13:58 A : [EMAIL PROTECTED] Objet : Big difference in MyISAM and InnoDB SELECT speed Hello, I am trying to optimize MySQL (3.23.49 from Debian stable) setup for ASPseek application. I decided to try InnoDB in order to be able to update tables while performing time cons

Big difference in MyISAM and InnoDB SELECT speed

Hello, I am trying to optimize MySQL (3.23.49 from Debian stable) setup for ASPseek application. I decided to try InnoDB in order to be able to update tables while performing time consuming selects. After converting all tables to InnoDB I noticed a big difference in processing speed of one of the

Re: InnoDB select slow too

Heikki Tuuri wrote: > > Chris, > > what is your my.cnf or my.ini like? Do you have a big enough > innodb_buffer_pool_size? set-variable = innodb_buffer_pool_size=300M big enough? Chris database, sql, query, table (just to keep the stoopid list software from whinging..) -

Re: InnoDB select slow too

Chris, what is your my.cnf or my.ini like? Do you have a big enough innodb_buffer_pool_size? Regards, Heikki http://www.innodb.com -- Order commercial MySQL/InnoDB support at https://order.mysql.com/ [EMAIL PROTECTED] wrote: > > Your message cannot be posted because it appears to be either s

Re: InnoDB select slow too

[EMAIL PROTECTED] wrote: > > Your message cannot be posted because it appears to be either spam or > simply off topic to our filter. To bypass the filter you must include > one of the following words in your message: > > database,sql,query,table > > If you just reply to this message, and incl

Fwd: Re: TEMPORARY + InnoDB + select coun(*) + Bye = mysqld crash

Heikki sent his response to the wrong address... -- Forwarded Message -- Subject: Re: TEMPORARY + InnoDB + select coun(*) + Bye = mysqld crash Date: 25 Apr 2001 17:18:06 - From: Heikki Tuuri <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Alex, MySQL obviously tries t

Re: TEMPORARY + InnoDB + select coun(*) + Bye = mysqld crash with signal 11.

Alex, MySQL obviously tries to drop the table when you exit from the mysql client, since the table is temporary. I have not tested TEMPORARY tables. I just tried on prerelease .38 and it does not work in that version either. I will fix it in .38 if Monty has not yet put out it. Regards, Heikki

TEMPORARY + InnoDB + select coun(*) + Bye = mysqld crash with signal 11.

Heikki, Mysql-3.23.36, Solaris 2.8. My mysqld crashes when I create a TEMPORARY InnoDB table from the console if I do a SELECT COUNT(*) before exiting from the console. No problem with MyISAM tables, no problem with no TEMPORARY table. mysql> CREATE TEMPORARY TABLE mybuffer ( id int