Hi Heikki,
OK! Thanks for the clarification.
-- Prabhu
On Mon, 31 Dec 2001, Heikki Tuuri wrote:
Date: Mon, 31 Dec 2001 17:26:57 +0200
From: Heikki Tuuri [EMAIL PROTECTED]
To: Rajarajeswaraprabhu [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB in MySQL-4.0.1
Hi!
Sorry
Hi!
It is a bug in the FOREIGN KEY syntax parser. It is confused by the column
name
e_foreigncurrency
The bug appears if the string 'foreign' is succeeded by a non-space
character in a CREATE TABLE statement.
Workaround: change the column name to e_currencyforeign, for example.
Fixed in
Mysql Row Locking
On Wed, 13 Feb 2002 [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:
sql,query
If you just reply to
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
In article 003b01c1b0a4$351665f0$540ec5c2@omnibook,
Heikki Tuuri [EMAIL PROTECTED] writes:
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync
TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Friday, February 08, 2002 3:50 PM
Subject: Re: InnoDB foreign keys crash MySQL
In article
://www.mysql.com
-Original Message-
From: Gurupartap Davis [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: Saturday, February 09, 2002 2:32 AM
Subject: Re: InnoDB File Size
Yes, I saw that before...My filesize was limited to 2GB before, but now
Yes, I saw that before...My filesize was limited to 2GB before, but now with
a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB data file
now, right?
So something's wrong... as I said before, I have successfully created a 9GB
file on this machine before, so the filesystem isn't to
09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
Harald,
Hi, Heikki!
...
I tested now with the official Linux binary of 4.0.1 (not -max) and it
worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
InnoDB startup options in my.cnf.
I just downloaded mysql
Hi!
From http://www.innodb.com/ibman.html :
MySQL/InnoDB-3.23.44, November 2, 2001
You can define foreign key constraints on InnoDB tables. An example: FOREIGN
KEY (col1) REFERENCES table2(col2).
You can create 4 GB data files in those file systems that allow it.
Thus 4 G files
://www.mysql.com
-Original Message-
From: Gurupartap Davis [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: Saturday, February 09, 2002 2:32 AM
Subject: Re: InnoDB File Size
Yes, I saw that before...My filesize was limited to 2GB before, but now
09, 2002 3:59 PM
Subject: Re: InnoDB foreign keys crash MySQL
Harald,
Hi, Heikki!
...
I tested now with the official Linux binary of 4.0.1 (not -max) and it
worked ok on our dual Xeon Linux-2.4.16-SMP-64GB. I did not define any
InnoDB startup options in my.cnf.
I just downloaded mysql
Harald,
I tested the below with 3.23.48, and it worked ok.
Could it be that you have not used DROP TABLE or DROP DATABASE to remove
InnoDB tables? Then the internal data dictionary may be out-of-sync from the
.frm files of your tables.
Please use innodb_table_monitor (section 9.1 in
TABLE MONITOR OUTPUT
==
-Original Message-
From: Harald Fuchs [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Friday, February 08, 2002 3:50 PM
Subject: Re: InnoDB foreign keys crash MySQL
In article
Yes, I saw that before...My filesize was limited to 2GB before, but now with
a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB data file
now, right?
So something's wrong... as I said before, I have successfully created a 9GB
file on this machine before, so the filesystem isn't to
On Friday 08 February 2002 16:32, Gurupartap Davis wrote:
Yes, I saw that before...My filesize was limited to 2GB before, but now
with a 2.4 kernel and reiserfs I _should_ be allowed to create a 20GB
data file now, right?
So something's wrong... as I said before, I have successfully created
Hi!
From http://www.innodb.com/ibman.html :
MySQL/InnoDB-3.23.44, November 2, 2001
You can define foreign key constraints on InnoDB tables. An example: FOREIGN
KEY (col1) REFERENCES table2(col2).
You can create 4 GB data files in those file systems that allow it.
Thus 4 G files
Martin,
use VARCHAR(255) instead of CHAR(255) to save space. Otherwise, InnoDB uses
the full 255 bytes to store the field.
There is however an exception to this: if you define any single column as
VARCHAR in the table, then MySQL silently changes all long CHAR column to
VARCHAR. These silent
To: Chetan Lavti
Cc: [EMAIL PROTECTED]
Subject: RE: InnoDB help !!
Hi,
On Wed, 2002-01-30 at 15:19, Chetan Lavti wrote:
It seems, you suggesting that after setting changes in the
configuration
file the Show variable. will list out the 'YES' in front of
'have_innodb' (in table below). right
it ??
Please, help me as much you can !! I have been stuck at this place.
Thanks and regards,
Chetan Lavti
-Original Message-
From: Arjen Lentz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 29, 2002 10:42 AM
To: Chetan Lavti
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB help !!
Hi
Matthew,
Tuesday, January 29, 2002, 6:37:32 AM, you wrote:
MW You can only do this while compiling it from source.
MW Matthew Walker
MW Ecommerce Project Manager
MW Mountain Top Herbs
MW -Original Message-
MW From: Chetan Lavti [mailto:[EMAIL PROTECTED]]
MW Sent: Monday, January 28,
Chetan,
Tuesday, January 29, 2002, 7:02:18 AM, you wrote:
CL thanks for reply,
CL but I have installed MySQL on Linux using the RPM files and while using
CL RPM files should I have to give the option while installing? As while
CL using the RPM files there is no compilation.
CL It is no where
Chetan,
Tuesday, January 29, 2002, 4:06:30 PM, you wrote:
CL thanks for your quick reply !!
CL that's fine !! I have done the max.RPM installation part.
CL but what is fix up the startup scripts so that
CL binary will be the one started.
CL When I am trying show variables like have_%;
CL
Hi,
On Wed, 2002-01-30 at 00:06, Chetan Lavti wrote:
thanks for your quick reply !!
that's fine !! I have done the max.RPM installation part.
but what is fix up the startup scripts so that
binary will be the one started.
When I am trying show variables like have_%;
Hi,
On Wed, 2002-01-30 at 15:19, Chetan Lavti wrote:
It seems, you suggesting that after setting changes in the configuration
file the Show variable. will list out the 'YES' in front of
'have_innodb' (in table below). right ??
Indeed.
The second thing is that, how do I test for the
Just add another file entry to my.cnf seperated by commas... You can add as
many seperate files as you like... (within reason of course, eventually if
the line length gets longer than 1024 or so you cant add anymore). Once you
edit the file, restart mysql and innobase will detect the new file
On Mon, Jan 28, 2002 at 09:30:59AM -0600, ryc wrote:
Hello,
is possible on the fly change size of innodb tables ??
i create table 1G large but is small and i need enlarge it. Can i
change number in my.cnf or something else ?
Just add another file entry to my.cnf seperated by
You can only do this while compiling it from source.
Matthew Walker
Ecommerce Project Manager
Mountain Top Herbs
-Original Message-
From: Chetan Lavti [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 28, 2002 9:11 PM
To: [EMAIL PROTECTED]
Subject: InnoDB help !!
hi,
I have downloaded
Hi,
On Tue, 2002-01-29 at 14:10, Chetan Lavti wrote:
I have downloaded and installed MySQL ( rpm's). Now, I want to configure
it with InnoDB option, as given in the manual,
but can't see the below configure file anywhere.
// cd /path/to/source/of/mysql-3.23.37
./configure --with-innodb
Jeremy,
look at http://www.innodb.com/ibman.html and http://www.innodb.com/todo.html
about InnoDB isolation levels.
Currently, SET TRANSACTION ISOLATION LEVEL does not have any effect on
MyISAM, BDB, or InnoDB.
The standard isolation level of InnoDB is REPEATABLE READ (you can also call
that
On Tue, Jan 15, 2002 at 08:36:16PM +0200, Heikki Tuuri wrote:
This brings up an interesting point. If you've lost your .frm
files, are you totally screwed, or does InnoDB contain enough
information to restore those .frm files? It's not a big deal if
With some work, yes.
PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: Friday, January 25, 2002 10:22 AM
Subject: Re: innoDB confusion
On Tue, Jan 15, 2002 at 08:36:16PM +0200, Heikki Tuuri wrote:
This brings up an interesting point. If you've lost your .frm
files, are you totally screwed, or does InnoDB contain
Hi!
HeikkiiH == Heikki Tuuri [EMAIL PROTECTED] writes:
HeikkiiH Ken,
HeikkiiH the 'connection lost' error suggests some bug in the client or
HeikkiiH communication. Since you are running 4.0.1-alpha, it could be something with
HeikkiiH the query cache. I think Sanja has already fixed some
On Fri, 19 Jan 2001, Byron Albert wrote:
Hello,
I have a few questions. First I work on a very high traffic site that
uses vbulletin 1.1 to run its bb. The bb is very high traffic around
60-200 concurrent users. We are starting to run into some serious
locking issues, and I am
Chris,
Hi there,
I've been experimenting with InnoDB and replication and now have a few
questions...Firstly, is it a known bug that SHOW TABLE STATUS screws up
InnoDB
transactions? To insert data into my innoDB table I've been using:
set autocommit=0;
INSERT ...
INSERT ...
...
commit;
In
On Mon, Jan 21, 2002 at 10:50:10PM +0200, Heikki Tuuri wrote:
this is a known 'feature' which is also mentioned in the
manual. SHOW TABLE STATUS will set an exclusive lock to the end of
table to look at the current auto-inc column value, which SHOW TABLE
STATUS has in its output. Since
I work for vBulletin and have some input on this. First off, you really
should look into upgrading to version 2.2.x, as not only are there many
new features, but there have been a number of performance enhancements
done that may help your situation. You also might want to take a look
at the
I've had a similar error when creating innodb tables, using a 4.0.1 client,
and a .47 server, if I loaded my create statement from a text file, the
innodb table wouldn't create. Change the type to myisam and it worked fine.
If I wound up creating it line by line, it worked fine. This might
Hi!
On Jan 17, Alexei V. Alexandrov wrote:
Hello everyone,
I`m running mysql version 4.0.0-alpha under FreeBSD 4.3-STABLE on a
dual pentium 4 x 1Ghz with a total memory of 1.5Gb and a scsi hard
drive with a volume about 50Gb. The problem is in the InnoDB startup
option
Ken,
the 'connection lost' error suggests some bug in the client or
communication. Since you are running 4.0.1-alpha, it could be something with
the query cache. I think Sanja has already fixed some bugs there since 4.0.1
was released. The query cache is suspect since the error did not crash the
Aaron,
please look at http://www.innodb.com/features.html,
http://www.innodb.com/division.html, and http://www.innodb.com/ibman.html
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for the online manual and
Aaron,
-Original Message-
From: Rutledge, Aaron [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Date: Tuesday, January 15, 2002 7:13 PM
Subject: RE: innoDB confusion
Thank You Heikki,
That information helps a lot. A couple quick questions if you dont
mind:
In regards
: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 10:43 AM
To: Rutledge, Aaron
Cc: [EMAIL PROTECTED]
Subject: Re: innoDB confusion
Aaron,
-Original Message-
From: Rutledge, Aaron [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Date: Tuesday, January 15, 2002 7:13
Do a show table status at the mysql prompt. Under type you should see
InnoDB.
--Walt Weaver
Bozeman, Montana
-Original Message-
From: Rutledge, Aaron [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 10:57 AM
To: Mysql List (E-mail)
Subject: RE: innoDB confusion
One final
, January 15, 2002 10:57 AM
To: Mysql List (E-mail)
Subject: RE: innoDB confusion
One final question, and I am done. You have helped me
tremendously--thank you. Wow, I really didn't expect the developer of
the software to answer my questions--this is terrific.
Is there way to verify
On Tue, Jan 15, 2002 at 08:17:53PM +0200, Heikki Tuuri wrote:
: Hi!
:
: Weaver, Walt wrote in message ...
: Do a show table status at the mysql prompt. Under type you should see
: InnoDB.
:
: Yes, and in really problematic situations, where you have lost your .frm
: files, for example, you can
Hi!
-Original Message-
From: Philip Molter [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, January 15, 2002 8:24 PM
Subject: Re: innoDB confusion
On Tue, Jan 15, 2002 at 08:17:53PM +0200, Heikki Tuuri wrote:
: Hi!
:
: Weaver
Molter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 11:24 AM
To: Heikki Tuuri
Cc: [EMAIL PROTECTED]
Subject: Re: innoDB confusion
On Tue, Jan 15, 2002 at 08:17:53PM +0200, Heikki Tuuri wrote:
: Hi!
:
: Weaver, Walt wrote in message ...
: Do a show table status at the mysql prompt
Woah...
Heikki Tuuri wrote:
With some work, yes. innodb_table_monitor prints the internal schema of
InnoDB. There are fewer column types inside InnoDB than in MySQL. For
example, a DATE column will appear as an integer.
Now I am confused again. Do you only have access to column types
Aaron,
Rutledge, Aaron wrote in message ...
Woah...
Heikki Tuuri wrote:
With some work, yes. innodb_table_monitor prints the internal schema of
InnoDB. There are fewer column types inside InnoDB than in MySQL. For
example, a DATE column will appear as an integer.
Now I am confused again. Do
PROTECTED]
Subject: Re: innoDB confusion
Aaron,
Rutledge, Aaron wrote in message ...
Woah...
Heikki Tuuri wrote:
With some work, yes. innodb_table_monitor prints the internal schema
of
InnoDB. There are fewer column types inside InnoDB than in MySQL. For
example, a DATE column will appear
capture this.
I'm running on Linux Redhat 6.2 with the 2.4 kernel, mysql 3.23.44.
Thanks,
-- Confused In Bozeman
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: Re: innoDB confusion
Hi!
Weaver
PROTECTED]]
Sent: Tuesday, January 15, 2002 11:18 AM
To: [EMAIL PROTECTED]
Subject: Re: innoDB confusion
Hi!
Weaver, Walt wrote in message ...
Do a show table status at the mysql prompt. Under type you should see
InnoDB.
Yes, and in really problematic situations, where you have lost your
Cool. Thanks, John.
--Walt
-Original Message-
From: John Kemp [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 1:06 PM
To: Weaver, Walt
Cc: [EMAIL PROTECTED]
Subject: Re: innoDB confusion
Walt,
It'll go to the database_machine_name.err file on that machine.
John
Weaver
Hi SAm,
I actually had a similar problem myself, but was unable to prove it was
the persistent connection itself causing this. I'm wondering if this
means that INNODB thinks that a connection that is now 'sleeping' (ie.
where a connection was created, used, but is now unused but still open)
Hi!
Looks like your are not committing your transactions. Every UPDATE and
INSERT automatically sets row level locks, which are only removed when you
do a COMMIT or ROLLBACK.
Or you have set innodb_lock_wait_timeout too small in my.cnf.
InnoDB does not set table level locks. Only LOCK TABLES
Heikki,
Hmm. That's interesting. So if you do a single command, say
INSERT INTO Table1 (X, Y, Z) VALUES ( A, B, C) ;
You actually need to write (I'm not sure of the exact transactional
syntax for Mysql) -
BEGIN ; --begin a transaction
INSERT INTO Table1 (X, Y, Z) VALUES ( A, B, C) ;
COMMIT ;
at https://order.mysql.com/
See http://www.innodb.com for the online manual and latest news on InnoDB
-Original Message-
From: John Kemp [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Wednesday, January 09, 2002 10:38 PM
Subject: Re: InnoDB
, autocommit is on.
--Walt Weaver
Bozeman, Montana
-Original Message-
From: John Kemp [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 1:40 PM
To: Heikki Tuuri
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB : Lock wait timeout exceeded; Try restarting
transaction
Heikki,
Hmm
PROTECTED]
Subject: Re: InnoDB : Lock wait timeout exceeded; Try restarting
transaction
Heikki,
Hmm. That's interesting. So if you do a single command, say
INSERT INTO Table1 (X, Y, Z) VALUES ( A, B, C) ;
You actually need to write (I'm not sure of the exact transactional
syntax
Hi!
It is a bug if the sleeping connection is in the auto-commit mode. But we
need more information of the problem. If you encounter it, please send the
exact sequence of SQL commands which leads to the problem.
You may also test
SET AUTOCOMMIT=1
explicitly in your program.
Note that LOCK
Heikki,
Thanks very muich for the explanation. That's an interesting question
for the connection modules in Apache/PHP/DBI etc. Perhaps this is a
problem with the way the connections are opened by those programs. I
hadn't thought of that, so it would definitely be a good thing to test
before
Hi!
-Original Message-
From: Peter Zaitsev [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Saturday, January 05, 2002 10:35 PM
Subject: Innodb/Replication problems.
Hello mysql,
I'm using mysql 3.23.47 with Innodb and trying to
On Thu, Dec 27, 2001 at 06:56:03PM +0200, Heikki Tuuri wrote:
* Recovery has been made more resilient to corruption of log files.
Can I ask what you mean here? If the log files are corrupt, is
recovery still possible then? Or are the log files themselves less
likely to get corrupted? I'm
Hi!
On Thu, Dec 27, 2001 at 06:56:03PM +0200, Heikki Tuuri wrote:
* Recovery has been made more resilient to corruption of log files.
Can I ask what you mean here? If the log files are corrupt, is
recovery still possible then? Or are the log files themselves less
likely to get corrupted?
-Original Message-
From: Rajarajeswaraprabhu [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Friday, December 28, 2001 6:53 AM
Subject: Re: InnoDB in MySQL-4.0.1
Hi Keikki,
I would like to know if row level privileges can be set
available
for row level privileges.
Thanks,
Prabhu
On Mon, 31 Dec 2001, Heikki Tuuri wrote:
Date: Mon, 31 Dec 2001 17:26:57 +0200
From: Heikki Tuuri [EMAIL PROTECTED]
To: Rajarajeswaraprabhu [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB in MySQL-4.0.1
Hi!
Sorry, I think
Innobase allows you to specify multiple data files and will use them
automatically. So to keep under the 2gb limit just keep adding 2gb files as
needed. You can see how much space is left in the innobase data files by
doing the following query: show table status from 'dbname' like
'tablename'.
Hi Keikki,
I would like to know if row level privileges can be set in mysql.
Eg:-
In user table, the user shall be allowed to edit only his record.
In a table for task report, only assignee of the task shall be
allowed to edit the specific record.
-- Prabhu
On Thu, 27 Dec
On Mon, Dec 17, 2001 at 10:03:58PM -0600, Philip Molter wrote:
: Is there any upcoming fix for this recurring problem? The table
: handler is just giving poor data to the optimizer and the optimizer
: is making bad decisions because of it. It appears to come and go,
: depending on data that is
Forwarded message:
Return-Path: [EMAIL PROTECTED]
From: Mehalick, Richard RE SITI-ITPSCA [EMAIL PROTECTED]
To: 'Heikki Tuuri' [EMAIL PROTECTED]
Subject: RE: Innodb Win2000 error
Date: Tue, 18 Dec 2001 11:41:45 -0600
Thank you for responding. I was just going to post again that I solved
Philip,
I recommend using the MySQL STRAIGHT JOIN and USE INDEX clauses to manually
force the best plan.
You could also use innodb_table_monitor to check that the key value set
cardinality estimates are approximately right for the tables h, pt, and p.
But to put it the other way, how could the
On Tue, Dec 18, 2001 at 11:19:06PM +0200, Heikki Tuuri wrote:
: Philip,
:
: I recommend using the MySQL STRAIGHT JOIN and USE INDEX clauses to manually
: force the best plan.
I'd love to, but I also have to maintain a spec of database
agnosticism (which I could do in code, of course, but I
Rich,
I have a system with 1gig of ram and i am trying to get the innodb buffer to
be about 750megs. Whenever I set the value in the database config file it
won't start with an error along the lines of,
011207 21:02:42 mysqld started
InnoDB: Fatal error: cannot allocate 67108864 bytes of
[mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 08, 2001 4:58 AM
To: [EMAIL PROTECTED]
Subject: Re: innodb won't allocate the memory i ask it to
Rich,
I have a system with 1gig of ram and i am trying to get the innodb buffer
to
be about 750megs. Whenever I set the value in the database config
Ah, I finally found mention of this in the manual.
Sorry to bother everyone.
Thanks.
---
Hello,
To use InnoDB you have to put how large of a file MySQL is allowed to make by putting
an entry in /etc/my.cnf such as the one I used:
innodb_data_home_dir =
Hi!
On Dec 04, Gurupartap Davis wrote:
I'm converting a table to innodb from myisam in mysql 4.0 and I was
wondering why it takes sooo long to do a SELECT COUNT(*)
MyISAM stores total number of rows in MYI file header.
It's read into memory when table is opened.
So for SELECT COUNT(*) FROM
Hi Chris,
Welcome to the MySQL list;^) good to see you here...
Any way I found a link which might explain why your InnoDB inserts take
longer, perhaps this may be the reason...
http://www.mysql.com/doc/S/E/SEC418.html
In inserts InnoDB uses the insert buffer to merge secondary index records
to
Norman Khine wrote:
Welcome to the MySQL list;^) good to see you here...
*grinz* It's weird being a newbie again :-P
In inserts InnoDB uses the insert buffer to merge secondary index records
to indexes in batches. That saves a lot of disk i/o. In rollback no such
mechanism is used, and
Just For My Info: does it take long for one insert. if so, what does
the insert statement look like. the reason i ask is becuase i use
InnoDB and inserted a few records and it was pretty quick. but maybe
thats becuase my statement was:
insert into table (user,email,firstname,lastname)
Joe Ellis wrote:
Just For My Info: does it take long for one insert. if so, what does
the insert statement look like. the reason i ask is becuase i use
InnoDB and inserted a few records and it was pretty quick. but maybe
thats becuase my statement was:
insert into table
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
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..)
Ashley,
Okay, so seeing Gemini failing, it was InnoDB's turn:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../../include -I../include
-DDBUG_OFF -O3 -DDBUG_OFF-DDEBUG_OFF -DUNIV_INTEL_X86 -c sync0sync.c
sync0sync.c: In function `sync_gnuc_intelx86_test_and_set':
sync0sync.c:187: impossible
Ashley,
On Thu, 22 Nov 2001, Ashley M. Kirchner wrote:
And while I'm sure someone is bound to tell me to stop using
RedHat's GCC 2.96 because of bad code, I'm sorry. Everything else
that I need/use compiles just fine and I never have problems with them,
except MySQL.
I would strongly
Hi!
I forwarded the email to Monty if he has time to look at index usage.
The speedup .43 - .44 may be due to better optimization of SQL queries, or
due to the table dumps and imports you made.
The way to defragment InnoDB tables, or tables in any database, is from time
to time to dump and
On Wed, 2001-11-21 at 05:19, Heikki Tuuri wrote:
The way to defragment InnoDB tables, or tables in any database, is from time
to time to dump and reimport them. That can give a significant performance
boost.
That is actually not entirely true. For MyISAM tables, one simply needs
to run
Hi!
On Wed, 2001-11-21 at 05:19, Heikki Tuuri wrote:
The way to defragment InnoDB tables, or tables in any database, is from time
to time to dump and reimport them. That can give a significant performance
boost.
That is actually not entirely true. For MyISAM tables, one simply needs
to
Hi!
Copied message:
..
Hi,
I'm a regular mysql user, and a very newbie to innodb. :)
I would like to use innodb because of its row-level locking feature.
Presently I have to use table locks, and they're causing lots of speed
problems. (I've tried Gemini tables, but mysql always crashed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Tue, 20 Nov 2001, Heikki Tuuri wrote:
When someone buys a particular type of good, I would like to lock those
rows from the table, but since the quantity will change, I don't even want
other users to see these rows until I'm finished.
On Thu, 15 Nov 2001 [EMAIL PROTECTED] wrote:
I am using 4.0 and switching from MyISAM to InnoDB,
so quite newbie on this:
I'm still using 3.23.4X (differs depending on which machine I'm on), but
I'm pretty sure that none of the questions have answers that change too
much between those
Hi!
You are getting a lock wait timeout error, not a crash. In the newest
version 3.23.44 code 101 has been replaced by a native MySQL error
number 1205 and a descriptive message.
Hi there.
Can anyone offer a solution to this problem.
CREATE TABLE `raw` (
`cid` int(11) default NULL,
Subject: Re: innodb inserts/select crash
Hi!
You are getting a lock wait timeout error, not a crash. In the newest
version 3.23.44 code 101 has been replaced by a native MySQL error
number 1205 and a descriptive message.
Hi there.
Can anyone offer a solution to this problem.
CREATE
fix it. It seems silly that I have to read
data out just to write it back in again instead of using the create...select
command.
Rich
Date: Tue, 13 Nov 2001 12:14:55
To: [EMAIL PROTECTED]
From: Heikki Tuuri [EMAIL PROTECTED]
Subject: Re: innodb inserts/select crash
Hi!
You are getting a lock
://www.innodb.com
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 02, 2001 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: InnoDB disk full problem
Wai,
Hi,
Help!!! Can anyone kindly tell me why InnoDB will take up 10 times table
space comparing
In the last episode (Nov 02), Stephen Lee said:
I have the following settings in /etc/my.cnf:
default-table-type=innodb
innodb_data_file_path = ibdata1:1000M
set-variable = innodb_log_file_size=5M
The resulting files:
-rw-rw1 mysqlmysql2560 Nov 2 12:17
In the last episode (Nov 02), Stephen Lee said:
I have the following settings in /etc/my.cnf:
default-table-type=innodb
innodb_data_file_path = ibdata1:1000M
set-variable = innodb_log_file_size=5M
The resulting files:
-rw-rw1 mysqlmysql2560 Nov 2 12:17
Hi,
how much of the 600MB actually is used at the moment
I'm sure there'a a better way to do it, but this one works:
mysql show table status like 'your_innodb_table' \G
...
Comment: InnoDB free: 3739648 kB
Best Regards,
Sasa
,
Heikki
http://www.innodb.com
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 19, 2001 3:11 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: innodb problem (with JDBC/transactions)
Erik,
run the MySQL server mysqld from a command prompt
Shakeel,
this may be a known problem. Another user running on
Solaris reported low CPU and disk i/o in connection
with queries taking a long time. The InnoDB Monitor
output he sent suggests Solaris has problems
scheduling a large number of threads.
I assume the problem is thread thrashing. I
1401 - 1500 of 1574 matches
Mail list logo
