InnoDB always needs the shared tablespace because it puts its
internal data dictionary and undo logs there. The .ibd files are
not sufficient for InnoDB to operate.
well, thats what I found before. But it doesn't explain why InnoDB
does need a logfile even when all transactions
Rob,
- Original Message -
From: Rob Brooks [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Sunday, March 12, 2006 6:02 PM
Subject: InnoDB Commit question
--=_NextPart_000_0033_01C645BC.03223720
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding
Hi, we have a db with myisam and a single innodb table. 2 separate
processes are inserting data into the myisam tables and the innodb table at
the same time. We have noticed an issue where commits to the innodb table
appear to be delayed until the process inserting into the myisam tables
I have some questions regarding InnoDB indices.
Say I have a table with millions of records. On of the fields is a type
field that has a possible value of 1,2,3, or 4. I sometimes query by the
type field and may at other times order on it.
Do queries benefit from an index with this low
Robert DiFalco [EMAIL PROTECTED] wrote on 03/09/2006 12:32:44 PM:
I have some questions regarding InnoDB indices.
Say I have a table with millions of records. On of the fields is a type
field that has a possible value of 1,2,3, or 4. I sometimes query by the
type field and may at other
- Original Message
From: Robert DiFalco [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thursday, March 9, 2006 9:32:44 AM
Subject: InnoDB Indices
I have some questions regarding InnoDB indices.
Say I have a table with millions of records. On of the fields is a type
field that has
deletes faster. But every
database engine handles this stuff differently.
R
-Original Message-
From: David Turner [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 10:13 AM
To: Robert DiFalco; mysql@lists.mysql.com
Subject: Re: InnoDB Indices
- Original Message
From
Robert,
actually, InnoDB always internally adds the PRIMARY KEY to every secondary
index record:
http://dev.mysql.com/doc/refman/5.0/en/innodb-table-and-index.html
If a column has just four different values, then in most cases an index on
that column does not help at all. And every index
Hi Foo,
MyISAM impress me on insert speed, however on many case MyISAM is not
better than Innodb. If you can't use combination of them,
better your break down your need to decide which one to use. AFAIK, sub
query is better in innodb rather than myisam, and if you have only
200.000 records
secs. But in InnoDB it is usually 8
secs. The time difference is too crazy to ignore.
Can anyone explain this? Is there something in InnoDB that creates the magic?
Innodb clusters the table data around the primary key... which is what
you're searching on. So your query is able to go right
tables: the original table will hold only enough fields for sorting, and
the huge fields in the other.
What do you guys think?
Ady Wicaksono wrote:
Hi Foo,
MyISAM impress me on insert speed, however on many case MyISAM is not
better than Innodb. If you can't use combination of them,
better your
*MySQL Manual - Chapter 12.7.4. Full-Text Restrictions* says: *Full-text
searches are supported for MyISAM tables only. *
You could try to do what i did... with some overhead... I also had InnoDB
tables for an application and also was in a great need of Full-Text
Searches.
I made a mirror MyISAM
?22,74279,74279#msg-74279
I need explanation about this issue :)
Heikki Tuuri wrote:
Ady,
- Original Message - From: Ady Wicaksono
[EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
With autocommit=1, anybody
: Lunes, 06 de Marzo de 2006 11:50 p.m.
To: mysql@lists.mysql.com
Subject: Re: Problem INNODB error 995
Osvaldo,
- Original Message -
From: Osvaldo Sommer [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, March 07, 2006 12:58 AM
Subject: Problem INNODB error 995
to the disks.
Osvaldo Sommer
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up
MyISAM tables
http://www.innodb.com/order.php
-Original Message-
From: Heikki
, like 90 secs. But in InnoDB it is
usually 8 secs. The time difference is too crazy to ignore.
Can anyone explain this? Is there something in InnoDB that creates the
magic?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com
As far as i know, using IN( SUBQUERY ) will give very poor performance,
especially if the record set returned by the large query is really large.
try to use a join instead of WHERE IN( XXX )..
Im not sure why its that much better in INNODB though...
Foo Ji-Haw wrote:
Hi all,
Just want
With autocommit=1, anybody could give calculation on how many rows could
be inserted in 1 seconds?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
We have 4 windows 2003 server with mysql 4.0.12 install in each one. They
have been working for about 1.5 years with no problem.
Two weeks ago, in one server we lost the mysql service, and when we look the
.err file it report a 995 error. We can star the service again and it works.
In the
Osku is working on FULLTEXT for InnoDB.
So, despite what the documentation says:
http://dev.mysql.com/doc/refman/5.0/en/fulltext-boolean.html
Which states:
They can work even without a FULLTEXT index, although a search executed in
this fashion would be quite slow.
You're saying that InnoDB
Speed of InnoDB Insert with autocommit=1;
Personal Test !
Linux : Fedora Core 4, kernel 2.6.11
mysqlgt; \s
--
mysql Ver 14.12 Distrib 5.0.18, for pc-linux-gnu (i686) using readline 5.0
Connection id: 2349
Current database: test
Current user: [EMAIL
Osvaldo,
- Original Message -
From: Osvaldo Sommer [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, March 07, 2006 12:58 AM
Subject: Problem INNODB error 995
--Boundary_(ID_PMYElD1sU13Il0ENO4J+aw)
Content-Type: text/plain;
charset=us-ascii
Content-Transfer
Daevid,
- Original Message -
From: Daevid Vincent [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, March 07, 2006 5:54 AM
Subject: RE: Boolean searches on InnoDB tables?
Osku is working on FULLTEXT for InnoDB.
So, despite what the documentation says:
http
Ady,
- Original Message -
From: Ady Wicaksono [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
With autocommit=1, anybody could give calculation on how many rows could
be inserted in 1 seconds
: Monday, March 06, 2006 5:32 PM
Subject: MySQL InnoDB Row insert Calculation
With autocommit=1, anybody could give calculation on how many rows could
be inserted in 1 seconds?
I am assuming that you perform a COMMIT after each insert.
If the computer does not have a battery-backed disk cache
hi guys, it's a simple thing (I think), but I can't find the docu on
this from the mysql site.
Thanks in advance for the help.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Daevid,
- Original Message -
From: Daevid Vincent [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Saturday, March 04, 2006 9:54 AM
Subject: Boolean searches on InnoDB tables?
I just discovered this:
http://dev.mysql.com/doc/refman/5.0/en/fulltext-boolean.html
Which
-search.html
Full-text indexes can be used only with MyISAM tables
When I try a query on an InnoDB table:
SELECT * FROM categories WHERE MATCH (name) AGAINST ('+ELECTRONICS' IN
BOOLEAN MODE);
I get:
Error Code : 1214
The used table type doesn't support FULLTEXT indexes
So, what is the deal? Am I
Concurrent inserts (there also may be concurrent reads going on) are
intermittently causing:
java.sql.SQLException: Lock wait timeout exceeded; try
restarting transaction
I noticed that adding innodb_table_locks=0 in my.ini fixes the problem.
Looking through the manual however, this
Robert,
please post SHOW INNODB STATUS\G during such lock wait, so that we see what
lock it is waiting for.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs
To: mysql@lists.mysql.com
Subject: Re: Lock wait timeout exceeded during concurrent inserts on an
InnoDB table
Robert,
please post SHOW INNODB STATUS\G during such lock wait, so that we see
what lock it is waiting for.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row
Robert,
maybe it was waiting on the AUTO-INC lock of the table? InnoDB must lock the
auto-inc counter, otherwise the MySQL replication would not work. That is a
limitation imposed by the MySQL architecture, not by InnoDB. InnoDB itself
never needs table locks.
Best regards,
Heikki
Oracle
Roberts
How many concurreent inserts you've done?
What MySQL version you use?
Concurrent inserts (there also may be concurrent reads going on) are
intermittently causing:
java.sql.SQLException: Lock wait timeout exceeded; try
restarting transaction
I noticed that adding
: Lock wait timeout exceeded during concurrent inserts on an
InnoDB table
Roberts
How many concurreent inserts you've done?
What MySQL version you use?
Concurrent inserts (there also may be concurrent reads going on) are
intermittently causing:
java.sql.SQLException: Lock wait
: Monday, February 20, 2006 8:36 PM
To: Robert DiFalco
Cc: mysql@lists.mysql.com
Subject: Re: Lock wait timeout exceeded during concurrent inserts on an
InnoDB table
Roberts
How many concurreent inserts you've done?
What MySQL version you use?
Concurrent inserts (there also may
Hi!
- Original Message -
From: [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, February 14, 2006 5:50 PM
Subject: MySql InnoDB
Hi,
I'v installed MySql on my machine and created a new tables.
when i open some table to alter it,i see in the COMMENT textbox
Brandon,
sorry, you cannot move .ibd files between installations. The ability to do
so is in the TODO, but I cannot promise any release date.
Currently, the only way to move individual InnoDB tables between
installations is the dump + import method.
Best regards,
Heikki
Oracle Corp
Patrick,
it should work. You have only shown a fragment of the application code.
Maybe there is a bug somewhere else. If you write a very simple test program
to test this, do you still get the duplicate values?
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level
(updateQuery); ..
c.commit();
c.setAutoCommit(true);
As you can demonstrate by running your For Update query on the same
InnoDB table row in two instances of the mysql client, a second
connection trying to execute your For Update query on a row already
locked by that query in another connection
Tables are locked on delete because, like an update, they are changing data.
Imagine issuing a REPLACE statement after a DELETE statement. If the
DELETE locks the table, then the REPLACE happens AFTER the DELETE, as
you wanted. If the DELETE does not lock the table, then it's possible
the
So where's the row locking?
I configure my database with Innodb + READ COMMITED, by this configuration
by using autocommit=1, delete should be done on data commited to disk.
Other thread should be able to insert/update.
CMIIW
Tables are locked on delete because, like an update
Innodb is not row-level locking -- it's memory-page-level-locking. A
memory page is usually small, so it's almost like row-level locking,
but not quite. Perhaps you're running up against that?
What does the query log say which queries were running? How do you
know it's the delete that's taking
I have also seen the table locking on deletes and even on large selects
with INNODB. I had converted to INNODB strictly for the row level
locking that is the biggest selling point of using INNODB.
So all the avantages of INNODB that are advertised (ie - row level
locking) are mis-represented
Hrm, I could be wrongthe MySQL site says innodb uses row-level
locking, and BDB uses page-level locking. But I remember reading that
Innodb uses memory page level locking. Am I wrong?
At any rate, even if InnoDB is page-level locking, you still get the
benefits on a page-level, which
Innodb is indeed row level locking. You are likely thinking of BDB
which uses memory page level locking.
gw
sheeri kritzer wrote:
Innodb is not row-level locking -- it's memory-page-level-locking. A
memory page is usually small, so it's almost like row-level locking,
but not quite. Perhaps
Innodb is not row-level locking -- it's memory-page-level-locking. A
memory page is usually small, so it's almost like row-level locking,
but not quite. Perhaps you're running up against that?
What does the query log say which queries were running? How do you
know it's the delete that's
I guess I don't understand this locking stuff. I have a InnoDB table that
has one thing in it, a counter. All I want to do is have multiple
instances of the code read this counter and increment it. I want to make
sure that each one is unique.
Here is what I am doing in java
Patrick Duda [EMAIL PROTECTED] wrote on 10/02/2006 16:28:56:
I guess I don't understand this locking stuff. I have a InnoDB table
that
has one thing in it, a counter. All I want to do is have multiple
instances of the code read this counter and increment it. I want to
make
sure
At 10:52 AM 2/10/2006, [EMAIL PROTECTED] wrote:
Patrick Duda [EMAIL PROTECTED] wrote on 10/02/2006 16:28:56:
I guess I don't understand this locking stuff. I have a InnoDB table
that
has one thing in it, a counter. All I want to do is have multiple
instances of the code read this counter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Duda wrote:
I guess I don't understand this locking stuff. I have a InnoDB table
that has one thing in it, a counter. All I want to do is have multiple
instances of the code read this counter and increment it. I want to
make sure
At 12:54 PM 2/10/2006, Mark Matthews wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Duda wrote:
I guess I don't understand this locking stuff. I have a InnoDB table
that has one thing in it, a counter. All I want to do is have multiple
instances of the code read this counter
Hi,
We'd like to be able to move certain innodb databases between machines
(some, but not all). This would help greatly with resyncing slaves and
for fast backups. I know that we can create table-spaces on a per-table
basis as described here.
http://dev.mysql.com/doc/refman/5.0/en/multiple
Why table locked on delete?
---TRANSACTION 0 476648265, ACTIVE 530 sec, process no 13965, OS thread id
3152999360 updating or deleting, thread declared inside InnoDB 293
mysql tables in use 1,* locked 1*
11090 lock struct(s), heap size 634176, undo log entries 930711
MySQL thread id 16831
I have a customer who has been in production for a few weeks now having
converted from MyISM to INNODB. We have been experiencing a few problems
with our application. With that said, could you take a look at the info
below from my show INNODB status and let me know if you see any problems
based
What are the problems you've been experiencing? Did you convert all tables?
How big is the database?
On 2/9/06, Shaun Adams [EMAIL PROTECTED] wrote:
I have a customer who has been in production for a few weeks now having
converted from MyISM to INNODB. We have been experiencing a few problems
Shaun,
the my.cnf looks ok. You might be able to raise the InnoDB buffer pool size
to 3G, but beware swapping.
SHOW INNODB STATUS looks ok, though it would be more informative if it were
taken during a typical workload.
Free buffers 0
Having free buffers 0 is very normal. Buffers
to replicate all our data
to a second database.
Now I have two different possible approaches:
1. All tables are of type InnoDB, except one table which is of type MyIsam =
the FULLTEXT searchable table. This searchable table would have a column with
searchable text and a few meta data columns
Hello.
Have a look here:
http://lists.mysql.com/mysql/194596
http://dev.mysql.com/doc/refman/5.0/en/innodb-tuning.html
If you feel uncomfortable with 10G ibdata size, you may want to
switch to per-file tablespace:
http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html
http
I currently have a customer who we switched over to INNODB from MyISM. It's
a Dell Server with 4GB or Memory and RHEL4 64-bit. It's a fairly big
database the size of the MyISM folders (before we converted to INNODB)
was about 2-3Gigs.
Questions:
1. The ibdata1 file size is 10GB. Does
Shaun Adams wrote:
1. The ibdata1 file size is 10GB. Does that sound right? Should this file
be this big?
That sounds right. Innodb seems to incur large space overheads. but with
the cost of diskspace nowadays...
2. Once a week, I have to perform HUGE insert imports into the database
:~ -Original Message-
:~ From: Shaun Adams [mailto:[EMAIL PROTECTED]
:~ Sent: Tuesday, February 07, 2006 4:32 PM
:~ To: mysql@lists.mysql.com
:~ Subject: INNODB Questions and Optimization help
:~
:~ Questions:
:~
:~ 1. The ibdata1 file size is 10GB. Does that sound right? Should
with INSERT INTO Y (t_y_time,and so on) SELECT
(t_x_time, ... and so on) FROM X
excluding t_y_id
The table should not be locked, right :D
Thx
Gleb Paharenko wrote:
Hello.
It seems that the problem is in the t_y_id auto_increment field. InnoDB
puts special AUTO-INC table lock
-imporrt my data process each time?
3. What if I'm running multiple databases with innodb tables on one mysql
server? I guess if I use innodb_file_per_table it will help me keep the file
sizes down and make it easier to drop and reload individual databases. Am I
correct here?
Thanks,
Grant
Ware
--quote-names --flush-logs --all-databases /volumes/
raid/snapshot.sql
You should read about those options, mysqldump has a ton of them.
For systems with only InnoDB tables this will take a point in time
snapshot. You could probably get away with a simpler command on a
test server
Hello.
It seems that the problem is in the t_y_id auto_increment field. InnoDB
puts special AUTO-INC table lock, and prevent other threads from
inserting into Y. See:
http://dev.mysql.com/doc/refman/5.0/en/innodb-auto-increment-column.html
Ady Wicaksono wrote:
Below is the SQL to create
Hi,
I recently converted some of my tables to innodb from myisam. I don't need
transactions or rollback capability, I switched because I needed row-level
locking. These are large tables with many rows and lots of INSERTS and UPDATES.
Since changing these tables, I've noticed some large
auto_increment field. InnoDB
puts special AUTO-INC table lock, and prevent other threads from
inserting into Y. See:
http://dev.mysql.com/doc/refman/5.0/en/innodb-auto-increment-column.html
Ady Wicaksono wrote:
Below is the SQL to create table Y
CREATE TABLE `Y` (
`t_y_id` int(11) NOT NULL
)
/var/lib/mysql/gentoo1-bin.01 (1 Gig in size)
/var/lib/mysql/gentoo1-bin.01 (1 Gig in size)
/var/lib/mysql/gentoo1-bin.01 (1 Gig in size)
...
/var/lib/mysql/gentoo1-bin.60 (1 Gig in size)
These all look like binary log files, they aren't exclusive to
InnoDB. You must have
I use MySQL 5.0.15
I have about 5 billion rows in table X, i create another table Y with
the same stucture with X
CREATE TABLE Y LIKE X;
Both X and Y is the InnoDB table, since i believe that both work on the
row locking models
I try to initiate 2 session
First session try to INSERT all
Hello.
According to:
http://dev.mysql.com/doc/refman/5.0/en/innodb-locks-set.html
INSERT ... SELECT set a non-next-key lock on each row. So in most cases
you should be able to insert the record into Y. Please, provide
the CREATE statement for table Y and the output of 'show variables
`t_idx11` (`in_sms_time`),
KEY `t_idx12` (`t_y_time`,`t_y_type`(3)),
KEY `t_idx13` (`t_y_city`(7))
) ENGINE=InnoDB DEFAULT CHARSET=latin1
And this is mySQL System Variables
NameValue
auto_increment_increment 1
auto_increment_offset 1
automatic_sp_privileges ON
back_log 50
Imagine American Idol where users vote on their Idols
Imagine that the system is using an innodb table... where
INSERTING is very fast might be concurrent BUT inserting is done
over HTTP and PHP (not enable multiple insert :(( )
Updating status for each data inserted is also very fast
Hi;
My query.log is full of 'show innodb status' queries.
How do I get this ascii log file not to log these. OR some help with a
grep script to copy the file without these lines.
I noticed the same in the logs of a 4.1 test server. I put it down to
MySQL Administrator which was monitoring
On 1/27/06, Imran Chaudhry [EMAIL PROTECTED] wrote:
Hi;
My query.log is full of 'show innodb status' queries.
How do I get this ascii log file not to log these. OR some help with a
grep script to copy the file without these lines.
I noticed the same in the logs of a 4.1 test server. I
2006/1/25, Nathan Gross [EMAIL PROTECTED]:
Hi;
My query.log is full of 'show innodb status' queries.
How do I get this ascii log file not to log these. OR some help with a
grep script to copy the file without these lines.
If you have a linux box (or any acceptable shell)
cat query.log | grep
Aye. -v. thanks!
-nat
On 1/26/06, Pooly [EMAIL PROTECTED] wrote:
2006/1/25, Nathan Gross [EMAIL PROTECTED]:
Hi;
My query.log is full of 'show innodb status' queries.
How do I get this ascii log file not to log these. OR some help with a
grep script to copy the file without these lines
Hi;
My query.log is full of 'show innodb status' queries.
How do I get this ascii log file not to log these. OR some help with a
grep script to copy the file without these lines.
Thanks
-nat
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http
There are many information about different logs in manual but innodb log file.
Please tell me where can i find it?
What's innodb log file different to binlog?
Where can i find data about redo and undo?
thanks
Hello.
Some information you can find here:
http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html
http://dev.mysql.com/doc/refman/5.0/en/innodb-checkpoints.html
Have a look to innobase/log/log0log.c file in MySQL source distribution.
wangxu wrote:
There are many information about
Can anyone help me with an InnoDB problem?
I am trying to create a sequence of related tables using InnoDB but I'm not
having a lot of luck. The script I'm running would work fine in DB2 but the
rules are obviously different in MySQL. I'm hoping someone can tell me how
to modify my script so
Rhino [EMAIL PROTECTED] wrote on 01/16/2006 10:30:33 AM:
Can anyone help me with an InnoDB problem?
I am trying to create a sequence of related tables using InnoDB but I'm
not
having a lot of luck. The script I'm running would work fine in DB2 but
the
rules are obviously different
- Original Message -
From: [EMAIL PROTECTED]
To: Rhino [EMAIL PROTECTED]
Cc: mysql mysql@lists.mysql.com
Sent: Monday, January 16, 2006 10:54 AM
Subject: Re: InnoDB table creation sequence
Rhino [EMAIL PROTECTED] wrote on 01/16/2006 10:30:33 AM:
Can anyone help me with an InnoDB
one can restrict how much disk
space a directory can use in Linux.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com
to convert
this (and other tables) into InnoDB engine.
I first tried using the innodb_file_per_table option but when running the
statement
ALTER TABLE invoice ENGINE=INNODB;
ERROR 1114 (HY000): The table '#sql...' is full
(this about one our after the start of the command, when the size
).
Since I have some performance troubles with table-locking in a multi-user
environment (when one of them performs a complex query all the other have to
wait up to 1 minute, which is not very nice...), I would like to convert
this (and other tables) into InnoDB engine.
I first tried using
from MyISAM to InnoDB on 5.0.18
Hi,
I think you should change the tmpdir variable value to a
directory which
have enough room to create your temp big table (by default,
it points to /tmp dir).
Regards,
Jocelyn
Patrick Herber a écrit :
Hello!
I have a database with a big table
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
Hi everyone,
I'm running MySQL 4.0.18 on Debian with a 2.6 linux kernel using ext3 as
the underlying filesystem for the database storage.
I currently have some InnoDB tables with the following structure:
Log_20060101 {
Monitor_id medium int,
Timestamp
would expect the use of thousands of tables effectively to disable
MySQL's caching capability, which is one of the biggest performance
boosters.
Alec
John McCaskey [EMAIL PROTECTED]
13/01/2006 17:20
To
MySQL mysql@lists.mysql.com
cc
Subject
Huge number of tables with InnoDB
using
InnoDB. MySQL will choose the best index and use it. Using this index
as the primary key instead of a separate index improves disk space usage
with InnoDB as the primary key doesn't require a separate index
structure but will order the rows correctly in the actual storage.
As to events
performance
boosters.
Alec
"John McCaskey" [EMAIL PROTECTED]
13/01/2006 17:20
To
"MySQL" mysql@lists.mysql.com
cc
Subject
Huge number of tables with InnoDB
Hi everyone,
I'm running MySQL 4.0.18 on Debian with a 2.6 linux kernel using ext3 as
the u
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/en
Hi,
My innodb installation is using per-table table spaces for every table
on the system.
I originally configured 4Gig for the shared table space.
However when I do a show table status I see the following.
Comment: InnoDB free: 6144 kB
So 6Meg free, I assumed this was 6Meg free
At 23:44 + 1/10/06, Marvin Wright wrote:
Hi,
My innodb installation is using per-table table spaces for every table
on the system.
I originally configured 4Gig for the shared table space.
However when I do a show table status I see the following.
Comment: InnoDB free: 6144 kB
So
George,
- Original Message -
From: George Law [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Sunday, January 08, 2006 10:10 PM
Subject: allocate space for innodb innodb_file_per_table
Hi All,
I am running mysql 5.0.18 with a innodb table of 9 GB (plus several
others
Hello.
Is there a specific innodb list?
There is an InnoDB forum:
http://forums.mysql.com/list.php?22
disablign the keys. I think I tried that, but with a table with 7 mil
rows, that takes longer than the load data :-\
Have you increased the myisam_sort_buffer_size variable
Hi All,
I am running mysql 5.0.18 with a innodb table of 9 GB (plus several others)
on suse linux 9.3 with 4 GB ram.
when doing a show table status command, this table shows Data_Free:0
I assume this is because it is the file per table setting, where the
tables fall outside of the main
to change a table from myISAM
to INNODB.
7 hours later, I killed off the process and tried to avoid a 'roll back'
by deleting the #sqlibd file. Several hours later... I was able to
finally bring up the server using innodb_force_recovery = 3, exported
everything using mysql_dump, then brought
Hi All,
forgot something in my other post:
machine is running suse 9.3, 2.6.11.4-20a-smp kernel.
Ok, I think I know the answer here... but just to make sure :)
4.1.14 ran with about 10 mysqld process.
skip-innodb was initially turned on in the my.cnf before the attempted
migration
Carl,
InnoDB does purge deleted rows from the ibdata files. Certain PostgreSQL
advocates have been spreading a claim that InnoDB would not do that, but the
claim is false.
If your ibdata file keeps growing indefinitely, please check with SHOW
INNODB STATUS that you do commit all your
1301 - 1400 of 5209 matches
Mail list logo
