Daevid,
That page looks a little misleading.
First, it says it's stored in main memory, not on disk.
Then it says that on server-startup, it finds the largest value in the
table, and initialized it to that. So it is disk-based on startup, and
then resides in memory thereafter.
This doesn't
://falconsoft.com/
(831) 425-4522
(831) 621-6299 (Fax)
- Original Message -
From: Visolve DB Team [EMAIL PROTECTED]
To: FalconSoft, Inc [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Wednesday, November 08, 2006 11:25 PM
Subject: Re: InnoDB + FULLTEXT
Hi,
Till MySQL 5.0 there was no support
Hi,
Till MySQL 5.0 there was no support for FULLTEXT by InnoDB. More info on:
www.innodb.com/innodbtalkUC2005.pdf
Thanks
ViSolve DB Team.
- Original Message -
From: FalconSoft, Inc [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thursday, November 09, 2006 6:28 AM
Subject: InnoDB
-
From: Visolve DB Team [EMAIL PROTECTED]
To: FalconSoft, Inc [EMAIL PROTECTED]; mysql@lists.mysql.com
Sent: Wednesday, November 08, 2006 11:25 PM
Subject: Re: InnoDB + FULLTEXT
Hi,
Till MySQL 5.0 there was no support for FULLTEXT by InnoDB. More info on:
www.innodb.com/innodbtalkUC2005
Message-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:16 PM
To: George-Cristian B=EErzan
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB messup
Can you just put the files back where they were originally?
Ordinarily that would be in the path set
On Thu, Oct 19, 2006 at 11:03:11AM -0500, Mazur Worden, Kathy wrote:
I had this problem just this morning and wound up fixing it by changing
the innodb data and log file directories to new folders in the .cnf
file. This enabled to server to start up (new data and log files were
created) and I
Can you just put the files back where they were originally?
Ordinarily that would be in the path set up in mysql - see SHOW
VARIABLES LIKE datadir
You do need to have your ibdata* files and ib_logfile* files all in
there, assuming you weren't using the file-per-table setup (if you
were then I am
To: George-Cristian Bîrzan
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB messup
Can you just put the files back where they were originally?
Ordinarily that would be in the path set up in mysql - see SHOW
VARIABLES LIKE datadir
You do need to have your ibdata* files and ib_logfile* files all
To: George-Cristian B�rzan
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB messup
Can you just put the files back where they were originally?
Ordinarily that would be in the path set up in mysql - see SHOW
VARIABLES LIKE datadir
You do need to have your ibdata* files and ib_logfile
-
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:16 PM
To: George-Cristian Bîrzan
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB messup
Can you just put the files back where they were originally?
Ordinarily that would be in the path set up in mysql - see SHOW
On Wednesday 18 October 2006 23:36, Dan Buettner wrote:
George-Cristian - is it possible that the *.frm files also got moved
about??
Nope. What I'm thinking is the logs got moved, server restarted, it created
new ones and...
--
George-Cristian Bîrzan
Network Engineer
03, 2006 1:39 PM
To: Rick James
Cc: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-model.html
If you are not doing replication, you might
Schwartz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 1:39 PM
To: Rick James
Cc: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb
; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
We'll do some testing with innodb_locks_unsafe_for_binlog but if this
fixes the problem then it is a pretty safe assumption that the problem
also exists with subqueries in DELETE and UPDATE and not just for that
one case of INSERT as the article points
: Robert DiFalco; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: Re: Innodb Locks
There is a detailed write-up on how locking works in the manual:
http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-model.html
If you are not doing replication, you might check out
: Re: Innodb Locks
It's not a bug in InnoDB. There are far more knowledgeable people than
I on this list, but it should get a share-mode lock on anything it
selects from, otherwise there might be inconsistencies as it tries to
serialize different transactions into the binary log for replication
: 860.674.8341
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 2:42 PM
To: Baron Schwartz
Cc: Rick James; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Then I guess I am not understanding why re-writing
@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
It probably uses a single lock to handle a JOIN, and two locks to handle
a sub-SELECT. I doubt that it helps, but if I'm right it will change
what you see when you poking around.
Regards,
Jerry Schwartz
Global Information Incorporated
195
: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006 11:50 AM
To: Jerry Schwartz; Baron Schwartz
Cc: Rick James; mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Right, as I understand it the query optimizer in 5.2 will
simply rewrite
these sub selects
In the last episode (Oct 09), Ow Mun Heng said:
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's own rather
than have it all in 1 file. My belief is that it would be
- Original Message -
From: Dan Nelson [EMAIL PROTECTED]
To: Ow Mun Heng [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Monday, October 09, 2006 9:12 AM
Subject: Re: InnoDB, 1 file per table or 1 BIG table?
In the last episode (Oct 09), Ow Mun Heng said:
Just wanted to know
In the last episode (Oct 09), James Eaton said:
From: Dan Nelson [EMAIL PROTECTED]
I don't think that the number of files has any impact on query
speed. The advantage file-per-table gives you is the ability to
recover unused space easily by running OPTIMIZE TABLE. With a
single tablespace,
On Oct 9, 2006, at 7:15 AM, Ow Mun Heng wrote:
Hi All,
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's own rather than
have it all in 1 file.
My belief is that it would be
- Original Message -
From: Bruce Dembecki [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Cc: Ow Mun Heng [EMAIL PROTECTED]
Sent: Monday, October 09, 2006 3:13 PM
Subject: Re: InnoDB, 1 file per table or 1 BIG table?
There are some minor performance benefits here when run against
On Mon, 2006-10-09 at 15:42 -0600, James Eaton wrote:
- Original Message -
From: Bruce Dembecki [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Cc: Ow Mun Heng [EMAIL PROTECTED]
How do you go about converting InnoDB databases from the single tablespace
to those using the
On Mon, 2006-10-09 at 14:13 -0700, Bruce Dembecki wrote:
On Oct 9, 2006, at 7:15 AM, Ow Mun Heng wrote:
Hi All,
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's
Any thoughts on this? Should SomeTable be locked when performing the
UPDATE on AnotherTable?
---
Is there a detailed source for when innodb creates row or table locks?
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE
IN (SELECT id FROM t);
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:26 AM
To: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Any thoughts on this? Should SomeTable be locked when performing the
UPDATE
On 10/2/06, Robert DiFalco wrote:
Is there a detailed source for when innodb creates row or table locks?
The sourcecode.
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE SomeTable.id = N;
This is invoked after another thread
To: mysql@lists.mysql.com
Subject: Re: Innodb Locks
On 10/2/06, Robert DiFalco wrote:
Is there a detailed source for when innodb creates row or table locks?
The sourcecode.
I have a situation where one thread is performing this in one
transaction:
UPDATE SomeTable SET WHERE
AnotherTable
SET...
WHERE id IN (SELECT id FROM t);
-Original Message-
From: Robert DiFalco [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:26 AM
To: mysql@lists.mysql.com; [EMAIL PROTECTED]
Subject: RE: Innodb Locks
Any thoughts on this? Should SomeTable be locked
The error message says to go to
http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html to learn
how to set the different recovery options for innodb.
On 9/21/06, Sayed Hadi Rastgou Haghi [EMAIL PROTECTED] wrote:
Dear all,
our DB server crashed and when I try to start Mysql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I need some inputs regarding my.cnf :
We are using INNODB in our application.We have around 10
million records in the database. This will size up to
around 10GB of data.
Could you please suggest a sample my.cnf for this
configuration.
Hi,
Attached is the sample my.cnf for Innodb engine type.
Thanks,
ViSolve DB Team.
- Original Message -
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Friday, September 08, 2006 7:31 PM
Subject: INNODB my.cnf
Hi All,
I need some inputs regarding my.cnf :
We are using
Tripp,
ibdata files never shrink. You can try this to free up space:
* Take a mysqldump of all tables that you may need,
* delete the ibdata files,
* Rebuild your tables by importing the dump.
Using innodb_file_per_table, will freed the disk space whenever you
run optimize table or
Hopefully you're not still having this problem. I don't use
phpMyAdmin, but I know that it allows you to run repair table to try
to fix a table after a crash. Does that work?
-Sheeri
On 6/25/06, Khaled Jouda [EMAIL PROTECTED] wrote:
Hello,
I am having a problem with one of my MySQL
I did read in the manual that the field level REFERENCES constraints
on InnoDB tables do not work as expected and one has to first define a
table level index and then create a table-level FOREIGN KEY constraint
for the field to make it work.
I believe this is just a hack to keep things
Look at this previous thread
http://forums.mysql.com/read.php?22,42721,42721
Kishore Jalleda
http://kjalleda.googlepages.com
On 6/15/06, Vitaliy Okulov [EMAIL PROTECTED] wrote:
Здравствуйте, .
Hi all. I try to increaseinnodb_buffer_pool_size
There is log file:
mysqld_safe[23845]:
Vitaliy,
- Original Message -
From: Vitaliy Okulov [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, May 26, 2006 5:28 PM
Subject: innodb database crash
Hi all. I have some InooDB mysql crush logs, can somebody explain what
they mean?
Quote:
060525 18:09:43
Andrew,
a possible reason for the corruption is that you have enabled write caching
in the disk controller or in the disk, but those caches are not
battery-backed. Then a hard reboot may destroy the contents, and the
database becomes corrupt.
What kind of hardware are you using? Do you have
Hi Ben,
Try doing
SHOW ENGINES;
and see what it says. It should say InnoDB is supported, if not then it
hasn't compiled in.
Regards
---
** _/ ** David Logan
*** _/ *** ITO Delivery Specialist
Logan, David (SST - Adelaide) wrote:
Hi Ben,
Try doing
SHOW ENGINES;
Here: (pertinent cols only)
++--+--+-++
| Engine | Support | Transactions | XA | Savepoints |
++--+--+-++
| CSV|
ent
---
-Original Message-
From: Ben Clewett [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 23 May 2006 5:50 PM
To: Logan, David (SST - Adelaide)
Cc: mysql@lists.mysql.com
Subject: Re
: Tuesday, 23 May 2006 5:50 PM
To: Logan, David (SST - Adelaide)
Cc: mysql@lists.mysql.com
Subject: Re: InnoDB problems under 5.1.9
Logan, David (SST - Adelaide) wrote:
Hi Ben,
Try doing
SHOW ENGINES;
Here: (pertinent cols only)
++--+--+-++
| Engine
Ben Clewett wrote:
Dear MySQL,
I've installed 5.1.9 from source on a SUSE 10 box. But I can't get
InnoDB tables respected.
I have used the correct compilation flag (--with-innodb).
SHOW VARIABLES; lists all the usual innodb variables.
The innodb table space has been created in
Hi Gerald,
I am sure I don't have this in my my.cfg. I am using the supplied
'large table' my.cfg. The *only* innodb option I have is the command
line parameter to mysqld:
--innodb
If anybody has any other options about how to get innodb working in
5.1.9, I'd be very interested!
Thanks
Hi Gerald,
I am sure I don't have this in my my.cfg. I am using the supplied
'large table' my.cfg. The *only* innodb option I have is the command
line parameter to mysqld:
--innodb
If anybody has any other options about how to get innodb working in
5.1.9, I'd be very interested!
Thanks
Ben, what does SHOW ENGINES show you? It should list all known storage
engines and indicate whether your MySQL install supports it or not.
Here's mine (5.0.21) for comparison; I was able to create a test table
as InnoDB and the SHOW CREATE showed it as InnoDB:
- show engines;
Hi Dan,
This is what I have. What does this mean with regards to InnoDB?
++--++--+-++
| Engine | Support | Comment
| Transactions | XA | Savepoints |
Ben, looks like you've either got it disabled in my.cnf or with a
startup flag, or you've not set all the needed options for InnoDB.
See http://dev.mysql.com/doc/refman/5.0/en/mysqld-max.html, near the
bottom of the page it explains what DISABLED means and refers you to the
error log for
Thanks for the excellent reference, this gives me a lot to go on.
My server is in bits at the moment, I'll let you know when it's up again!
Ben
Dan Buettner wrote:
Ben, looks like you've either got it disabled in my.cnf or with a
startup flag, or you've not set all the needed options for
Thanks for the tip.
Simple problem, my innodb data file was created with the default my.cnf.
When I started it with the large_table version, it used different innodb
table space size. Therefore would not start :)
Cheers,
Ben
Dan Buettner wrote:
Ben, looks like you've either got it
Well, you're going to need to state how big a record is, what OS
platform you're using, what MySQL version you're using, and exactly
what error message you get when you're trying to insert that 5th
record.
Your my.cnf would help, too.
-Sheeri
On 5/22/06, Eko Budiharto [EMAIL PROTECTED] wrote:
: Friday, May 05, 2006 10:50 PM
Subject: Re: InnoDB Memory Problem causing mysql to crash
Well, according to my calculations:
innodb_buffer_pool_size + key_buffer_size
+ max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size)
+ max_connections*2MB
(I used the default
- Original Message -
From: sheeri kritzer [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, May 05, 2006 10:50 PM
Subject: Re: InnoDB Memory Problem causing mysql to crash
Well, according to my calculations:
innodb_buffer_pool_size + key_buffer_size
+ max_connections
Well, according to my calculations:
innodb_buffer_pool_size + key_buffer_size
+ max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size)
+ max_connections*2MB
(I used the default binlog_cache_size value of 32K plus your settings)
MySQL could use up to 4.991913 G of memory.
: mailing.database.myodbc
Sent: Friday, May 05, 2006 10:50 PM
Subject: Re: InnoDB Memory Problem causing mysql to crash
Well, according to my calculations:
innodb_buffer_pool_size + key_buffer_size
+ max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size)
+ max_connections*2MB
(I used
but you don't know __when__ innodb_file_per_table was set!
So it's possible that many innodb tables actually reside in ibdata
[1-4].
Check your data directory to see the individual innodb files/tables
(*.ibd).
This is true, and even on a fresh install that has always had
On Apr 26, 2006, at 3:54 AM, Dr. Frank Ullrich wrote:
Duzenbury, Rich wrote:
Hi all,
I've inherited an innodb database that is configured like:
innodb_file_per_table
innodb_data_file_path =
ibdata1:3000M;ibdata2:3000M;ibdata3:3000M;ibdata4:3000M:autoextend
Um, doesn't this allocate 12G that
Duzenbury, Rich wrote:
Hi all,
I've inherited an innodb database that is configured like:
innodb_file_per_table
innodb_data_file_path =
ibdata1:3000M;ibdata2:3000M;ibdata3:3000M;ibdata4:3000M:autoextend
Um, doesn't this allocate 12G that winds up being unused, since
innodb_file_per_table is
Todd
you need to look at how InnoDB is configured and learn a bit about how Innodb
uses and manages its tablespace. if you look in the my.ini options file you
should see how innodb is set up for your installation. Take a look at the
link below that explains how InnoDB can be set up:
Look at your my.cnf for a configuration directive called
'innodb_data_file_path'. This is where you configure the files for the
innodb table space. The last one is probably an auto-grow. My guess is that
every time it complains, it's just added 8MB to the file. If you remove the
auto-grow (and I
Hi.
Thanks for your response
[EMAIL PROTECTED] wrote:
Do you have any idexes on the table?
No.
The table looks like this.
Would there be any advantage in creating indexes for it?
| id | | LastUpdated|
| 32957c615b37b5674f99d1cfd06d6a23 | |
Do you have any idexes on the table?
What does your
mysql show create table tbl_name \G
statement look like please?
Keith
In theory, theory and practice are the same;
in practice they are not.
On Thu, 13 Apr 2006, Luke Vanderfluit wrote:
To: mysql@lists.mysql.com
From: Luke Vanderfluit
Hi
Can you through us more lights on error ? where does this occur ?
-bash-2.05b$ perror 10 30
OS error code 10: No child processes
OS error code 30: Read-only file system
-bash-2.05b$
-Praj
On Wed, 5 Apr 2006 08:48:08 +0700
Truong Tan Son [EMAIL PROTECTED] wrote:
[S] Dhandapani wrote:
Prasanna Raj [EMAIL PROTECTED] wrote:
Can you through us more lights on error ? where does this occur ?
**ERROR:
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and
Gotit Thnx ;)
You have set innodb_force_recovery to 3 which means , do not run transaction
rollbacks after recovery.
Just try removing the innodb_force_recovery from my.cnf file or change the
value
More info : http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
--Praj
On Wed, 5 Apr
Prasanna Raj [EMAIL PROTECTED] wrote:
Gotit Thnx ;)
You have set innodb_force_recovery to 3 which means , do not run transaction
rollbacks after recovery.
http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
1 (SRV_FORCE_IGNORE_CORRUPT)
2 (SRV_FORCE_NO_BACKGROUND)
3
Try going to:
http://www.mysql.com/innodb rollback
You can search the manual by typing http://www.mysql.com/search term
into the address bar of your browser. The first hit looked like a
winner to me.
-Sheeri
On 4/4/06, Truong Tan Son [EMAIL PROTECTED] wrote:
Dear Sir,
I install MySQL
[S] Dhandapani wrote:
mysql show global variables like '%innodb%';
+-++
| Variable_name | Value |
+-++
| have_innodb | YES
Hello Heikki,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
the complete log is about 50 mb, since a lot of errors occur.
I am interested in what caused the very first crash in the server. Now your
database seems to be seriously corrupt, since the log sequence
Marten,
Marten Lehmann wrote:
Hello Heikki,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
the complete log is about 50 mb, since a lot of errors occur.
I am interested in what caused the very first crash in the server. Now
your
database seems to be seriously
Well,
ok, we need to stress this more in the manual. A few users have
misunderstood that ibdata files would no longer be needed if one uses
innodb_file_per_table.
ib_logfiles are always needed. How else can InnoDB recover after a crash.
but how can I repair my existing ib-files so that the
Marten,
- Original Message -
From: Marten Lehmann [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Wednesday, March 29, 2006 7:52 PM
Subject: Re: innodb errors on startup
Well,
ok, we need to stress this more in the manual. A few users have
misunderstood that ibdata
Marten,
I replied today to your earlier email with the message pasted below.
Regards,
Heikki
Marten,
can you email the complete .err log from the server to
[EMAIL PROTECTED]
I am interested in what caused the very first crash in the server. Now your
database seems to be seriously
Bill Adams wrote:
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
Marten Lehmann wrote:
I had a lot of trouble today because the InnoDB integration in MySQL
is lousy. I read the manual and worked with innodb_per_file_table. So
when I shutdown mysql I should be able to delete ib_logfile0,
ib_logfile1 and ibdata1, because all table-data should be stored in
On Mar 21, 2006, at 1:08 PM, Marten Lehmann wrote:
I had a lot of trouble today because the InnoDB integration in
MySQL is lousy. I read the manual and worked with
innodb_per_file_table. So when I shutdown mysql I should be able to
delete ib_logfile0, ib_logfile1 and ibdata1, because all
Hello,
This is spelled out pretty clearly in the manual:
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
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 are
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:
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
-
From: Robert DiFalco [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Thursday, March 09, 2006 8:41 PM
Subject: RE: InnoDB Indices
=20
++ I can't see it helping with insert, but depending on the where
clause on your updates and deletes it could.
I guess I was thinking
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
Subject: Re: InnoDB and locking
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
Patrick,
c.setAutoCommit(false);
...
rs = statement.executeQuery(select request_id from requestid_innodb
for update);
...
String updateQuery = update requestid_innodb set request_id=;
updateQuery = updateQuery + nextRequestId;
tempStatement = c.createStatement();
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, they are
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
To: Ady Wicaksono
Cc: mysql@lists.mysql.com
Subject: Re: Innodb table locked on delete
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
in InnoDB because row-level locks fit in very little
space.
-Original Message-
From: sheeri kritzer [mailto:[EMAIL PROTECTED]
Sent: Friday, February 10, 2006 9:52 AM
To: Ady Wicaksono
Cc: mysql@lists.mysql.com
Subject: Re: Innodb table locked on delete
Innodb is not row
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
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 that
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 that
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
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
301 - 400 of 1574 matches
Mail list logo
