AW: InnoDB Corrupted databases (innodb_force_recovery not working)
Baron, Thanks alot for your reply - I am trying out these tools today. Lukas Lukas C. C. Hempel CEO Delux Group - Approaching future. www.delux.me Postfach 10 02 10 D-48051 Münster Mail: lu...@delux.me This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Delux Credit: www.delux-credit.com Delux Host: www.delux-host.com Delux Software: www.delux.me Admin panel: http://admin.delux-host.com Paypal: pay...@delux-host.com Delux is a company of Lukas Hempel, Tax ID: 337/5105/2023 -Ursprüngliche Nachricht- Von: baron.schwa...@gmail.com [mailto:baron.schwa...@gmail.com] Im Auftrag von Baron Schwartz Gesendet: Montag, 14. Dezember 2009 22:57 An: Lukas C. C. Hempel Cc: mysql@lists.mysql.com Betreff: Re: InnoDB Corrupted databases (innodb_force_recovery not working) Lukas, If you can't get innodb_force_recovery to work, then you might have to try to recover the data with these tools: http://code.google.com/p/innodb-tools/ Regards Baron -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=lu...@delux-host.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
AW: InnoDB and foreign keys
HELLO does anybody know if Foreign keys increase the performance of select querys? example. DB1 has only INNODB tables. DB2 has the same structure as DB1 with all possible foreign keys. is the same query faster on DB1 or DB2? Why should it increase performance? At the moment I have the hole database with MyIsam tables but there is very much data on it. I have more tables with over 500.000 record and over 100 MB but until now all queries are fast. The problem is that sometime happens that tables are corrupt and I have to REPAIR they. (mysql 4.1.5). All operations on the corrupt tables until REPAIR will fail and this is a big problem because more hundred people are working on the database at the same time and then much data will be lost. Now, I tried on a testdatabase to convert the tables to InnoDB to be more stable and to have transactions. The result is that all operations (select queries) are verry verry slow. Not as fast as on MyISAM. How could I increase the performance of my InnoDB, now? I hoped that it could be done with foreign keys but it not seems so... does anybody have other ideas for solving the problem? thanks... Uli -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: AW: InnoDB and foreign keys
Suggestions? Check your indexes. It sounds as though they aren't what they used to be. When you converted to InnoDB, did you accidentally move the data to a slower drive? If so, you may want to move it back to where you had the MyISAM tables. Shawn Green Database Administrator Unimin Corporation - Spruce Pine Ulrich Seppi [EMAIL PROTECTED] wrote on 10/13/2004 12:29:22 PM: HELLO does anybody know if Foreign keys increase the performance of select querys? example. DB1 has only INNODB tables. DB2 has the same structure as DB1 with all possible foreign keys. is the same query faster on DB1 or DB2? Why should it increase performance? At the moment I have the hole database with MyIsam tables but there is very much data on it. I have more tables with over 500.000 record and over 100 MB but until now all queries are fast. The problem is that sometime happens that tables are corrupt and I have to REPAIR they. (mysql 4.1.5). All operations on the corrupt tables until REPAIR will fail and this is a big problem because more hundred people are working on the database at the same time and then much data will be lost. Now, I tried on a testdatabase to convert the tables to InnoDB to be more stable and to have transactions. The result is that all operations (select queries) are verry verry slow. Not as fast as on MyISAM. How could I increase the performance of my InnoDB, now? I hoped that it could be done with foreign keys but it not seems so... does anybody have other ideas for solving the problem? thanks... Uli -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: AW: InnoDB and foreign keys
If you could post your table schema (SHOW CREATE TABLE table_name) and then give an example of the query that is slow on InnoDB that would help us give a better analysis. Right now it sounds like something is wrong, InnoDB is likely to be slightly slower than MyISAM because of transaction overhead and row level locking for simple selects. But, it should not be 'very very slow' if MyISAM is 'very very fast' as it sounds like you are saying. John On Wed, 2004-10-13 at 18:29 +0200, Ulrich Seppi wrote: HELLO does anybody know if Foreign keys increase the performance of select querys? example. DB1 has only INNODB tables. DB2 has the same structure as DB1 with all possible foreign keys. is the same query faster on DB1 or DB2? Why should it increase performance? At the moment I have the hole database with MyIsam tables but there is very much data on it. I have more tables with over 500.000 record and over 100 MB but until now all queries are fast. The problem is that sometime happens that tables are corrupt and I have to REPAIR they. (mysql 4.1.5). All operations on the corrupt tables until REPAIR will fail and this is a big problem because more hundred people are working on the database at the same time and then much data will be lost. Now, I tried on a testdatabase to convert the tables to InnoDB to be more stable and to have transactions. The result is that all operations (select queries) are verry verry slow. Not as fast as on MyISAM. How could I increase the performance of my InnoDB, now? I hoped that it could be done with foreign keys but it not seems so... does anybody have other ideas for solving the problem? thanks... Uli -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
AW: InnoDB
thanks a lot, I managed it now. was just a little misconfigured my.cnf-file -Ursprüngliche Nachricht- Von: Victoria Reznichenko [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 19. Februar 2003 14:34 An: [EMAIL PROTECTED] Betreff: re: InnoDB On Wednesday 19 February 2003 13:21, Rusch (ext) Reiner wrote: I have one question about InnoDB-tables especial the filesize of all tables. In the past I took MyISAM but found out, some things in InnoDB make the system more stable. But I want to get more free space. In MyISAM the space grows automatically, but not in InnoDB by default. Take a look at autoextend option: http://www.mysql.com/doc/en/InnoDB_start.html In my /etc/my.cnf the line for the path and file size is not active like in the original file. But it works but with about 250-300MB max. size (don't know exactly). If I uncomment this line to expand my space, mysql (4.0.10) doesn't start. Don't know why. Check error logs. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
AW: InnoDB frightens me...
Hi :) Are there plans on creating more than on tablesspace plus making them selectable ? So that I can tell the DB: - in which datafiles to store the tablespace X - in which tablespace to store table Y With MYISAM we could simply move the data+index files to a separate disc, create symlinks and everthing was ok, with InnoDB all tables are on the same disc and there is no way to divide the i/o :( Sure, you can use raid. But you still have no say in how much i/o a given table may use. Regards -Ursprüngliche Nachricht- Von: Heikki Tuuri [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 3. März 2002 12:46 An: [EMAIL PROTECTED] Betreff: Re: InnoDB frightens me... Steve, I added an item to the TODO list at http://www.innodb.com/todo.html .. May, 2002: Make a data file auto-extendible. You can specify the last data file in innodb_data_file_path like this: ibdata1:50Mautoextend It will create a data file whose initial size is 50 MB, and InnoDB will automatically extend it in units of 10 MB when the data file becomes full. .. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ Speed up adding of features to MySQL/InnoDB through support contracts See http://www.innodb.com for the online manual and latest news on InnoDB -Original Message- From: Steve Rapaport [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Date: Sunday, March 03, 2002 12:18 AM Subject: InnoDB frightens me... I'm seriously considering switching to mysql-max so I can make my session handling table an Innodb type. Currently the mysql locking policy allows big traffic jams when several sessions are active simultaneously, and it's the only table that has frequent updates. I need row-locks! BUT, and it's a big but, I just read through the InnoDB manual pages in the mysql site, and it seems I can't have row-locking without a lot of programming and worse, admin overhead. And scary a-priori decisions. At first glance (correct me) I need to 1. Check through all my programs handling this table to add AUTOCOMMIT or Commit/Rollback as appropriate. 2. Decide with zero experience on a lot of maximum sizes which will not be adjustable in future, including dataspace. 3. If I run up against one of those limits in future I am guaranteed a nightmare of table copying, deleting, restoring, and woe if I happen to get a runaway rollback. I am also required to back up my database table and all its update logs in case of this situation, although my chances of restoring them successfully look dim. I am sufficiently frightened to just accept table-lock traffic jams instead. Can anyone tell me how I can use row-locking without getting into this frightening world? Best, Steve - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
AW: InnoDB frightens me...
Christian Rabe writes: Are there plans on creating more than on tablesspace plus making them selectable ? So that I can tell the DB: - in which datafiles to store the tablespace X - in which tablespace to store table Y This is one of the things I was wondering about.. If I have multiple InnoDB tablespaces, and I fire up the MySQL command-line client and issue a Create Table... TYPE=InnoDB, how do I tell it I want the table created in InnoDB space #1 or #2...?? As far as I can tell, it would appear that MySQL/InnoDB get the deciding vote there.. Perhaps I'm just missing something.. -- Rick - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
AW: InnoDB frightens me...
As far my knowledge goes there is only 1 tablespace available atm. If you create new datafiles they will get appended to the one and only tablespace. IF there would be more than one tablespace you would need to specify one as default. You should also be able to ALTER a table to another tablespace. Regards, Christian -Ursprungliche Nachricht- Von: Rick Flower [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 4. Marz 2002 19:17 An: MySQL Mailing List Cc: Heikki Tuuri Betreff: AW: InnoDB frightens me... Christian Rabe writes: Are there plans on creating more than on tablesspace plus making them selectable ? So that I can tell the DB: - in which datafiles to store the tablespace X - in which tablespace to store table Y This is one of the things I was wondering about.. If I have multiple InnoDB tablespaces, and I fire up the MySQL command-line client and issue a Create Table... TYPE=InnoDB, how do I tell it I want the table created in InnoDB space #1 or #2...?? As far as I can tell, it would appear that MySQL/InnoDB get the deciding vote there.. Perhaps I'm just missing something.. -- Rick - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
