I know this is a emotive subject but PLEASE drop it from the MySQL list.
Thanks
Simon
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To
On Monday 06 January 2003 14:51, Daniel Kiss wrote:
Does anyone know why 'on update cascade' option does not work in InnoDB
foreign keys?
Is it supported anyway?
It's supported since 4.0.8:
http://www.mysql.com/doc/en/News-4.0.8.html
--
For technical support contracts, goto
Sam,
I think now it is time to stop what you have started. If you can't answer the
question then don't waste the time of thousand of users on this list with your
personal opinions and comments on people signatures. You can communicate with
the user directly, not through the list. Other wise it
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
She who is in my mind and mouth, I love her with all my heart and blood
We'll restore OUR Palestine
Did you know a democratic country named ISRAEL created in 1948 ?
How do u define democratic? country? Israel? created?
Sameh Attia wrote:
Hi,
I have a system running MySQL 3.23.41. I read many times about
InnoDB performance and that it is superior to the MyISAM one. I have a
table 'sessions' in a MyISAM format with about 20 milion records. Its
size is 2.5 GB; the index file is 1.1 GB. In mysql client I
select crap from blahblah where nobody_is_interested = 'Y'
sql,query
- Original Message -
From: Sameh Attia [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 06, 2003 7:32 PM
Subject: Re: InnoDB vs. MySQL performance Issue
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED
Sameh Attia ([EMAIL PROTECTED]) écrivait:
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
She who is in my mind and mouth, I love her with all my heart and blood
We'll restore OUR Palestine
Did you know a democratic country named ISRAEL created in 1948 ?
How
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
She who is in my mind and mouth, I love her with all my heart and blood
We'll restore OUR Palestine
Did you know a democratic country named ISRAEL created in
: Monday, January 06, 2003 3:28 PM
Subject: Re: InnoDB vs. MySQL performance Issue
Sameh Attia ([EMAIL PROTECTED]) écrivait:
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
She who is in my mind and mouth, I love her with all my heart and
blood
We'll
[EMAIL PROTECTED]
Sent: Monday, January 06, 2003 3:28 PM
Subject: Re: InnoDB vs. MySQL performance Issue
Sameh Attia ([EMAIL PROTECTED]) écrivait:
Sam Przyswa wrote:
Sameh Attia ([EMAIL PROTECTED]) écrivait:
She who is in my mind and mouth, I love her with all my heart
Gelu Gogancea ([EMAIL PROTECTED]) écrivait:
Peace to all,
This is not the right place for this kind of discussions.
Please STOP.
Also i have a suggestion for the administrator of this list:
-to forbidden all e-mail which have in subject or body, logo
/slogan/catchword which can be considered
Hi,
I'm sure that all the people from this list RESPECT in what you believe or
in values which are considered by you to be inviolable/holy.
I'M NOT JEWISH but i'm sure if you will see, like logo/slogan , something
like ...
I WILL LOVE YOU FOREVER WITH MY HEART AND MY BLOOD, BEN GURION.
... i'm
Gelu Gogancea wrote:
Hi,
I'm sure that all the people from this list RESPECT in what you believe or
in values which are considered by you to be inviolable/holy.
I'M NOT JEWISH but i'm sure if you will see, like logo/slogan , something
like ...
I WILL LOVE YOU FOREVER WITH MY HEART AND MY BLOOD,
Sameh,
The right table manager to use (MyISAM or InnoDB) really depends on the
type of work you are requiring of MySQL.
If you are mainly doing selects, and hardly any updates/deletes/inserts,
then MyISAM is faster. Its indexes, as far as I know, are smaller and more
efficient. However,
Maximo Migliari wrote:
Sameh,
The right table manager to use (MyISAM or InnoDB) really depends on
the type of work you are requiring of MySQL.
If you are mainly doing selects, and hardly any
updates/deletes/inserts, then MyISAM is faster. Its indexes, as far
as I know, are smaller and more
Sameh,
your innodb_buffer_pool_size seems a bit small. In the manual it says:
Set buffer pool size to 50 - 80 % of your computer's memory, but make
sure on Linux x86 total memory usage is 2 GB. Your setting means that
you have no more than 256MB RAM and that's not much for operations on
really
Well, its possible that it took 10 hours to complete the conversion, if the
table was big enough, this could be justified.
20 million records is a lot of records!
Also, don't forget to change the memory settings for InnoDB in my.cnf.
InnoDB is a different table manager to MyISAM, and as such,
Maximo Migliari ([EMAIL PROTECTED]) écrivait:
Sameh,
We r here to help one another solving their problems. Ive never posted any
solutions, to this list or another based on religion or something else but
the problem itself only. I invite all people here to read the Islamic
history of true muslims
Joe,
- Original Message -
From: Joe Smith [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Monday, December 23, 2002 6:41 AM
Subject: Innodb querry optimizer suddenly making TERRIBLE choices? Urgent,
Please help!
I'm in a bit of a tough spot -- My innodb table of
On Thu, 19 Dec 2002, Deepa wrote:
While creating InnoDB tables, I was not able to specify a fulltext
column in the table creation sql. Is this a bug or a limitation with InnoDB
? There could be quite a few users who need FULLTEXT feature with InnoDB.
It's a feature :-(
FULLTEXT has not yet
At 10:35 -0500 12/19/02, Deepa wrote:
While creating InnoDB tables, I was not able to specify a fulltext
column in the table creation sql. Is this a bug or a limitation with InnoDB
? There could be quite a few users who need FULLTEXT feature with InnoDB.
It's like the manual says: FULLTEXT is
Hi!
Please send your postings to [EMAIL PROTECTED] The newsgroup
mailing.database.mysql is only a mirror of that mailing list.
The error message below is misleading. It should really be 'Cannot update a
parent row...'. Internally InnoDB does the update by deleting and
reinserting the index
Walt,
- Original Message -
From: walt [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, December 17, 2002 1:58 AM
Subject: innodb/mysql slow returning anything other than primary key
I've run into an interesting problem. I have a large innodb table (2274962
rows, 46
already in the root. This could cause unnecessary
table scans in SQL queries.
...
Regards,
Heikki
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 18, 2002 1:33 AM
Subject: Re: innodb/mysql slow returning anything other than primary key
Patricio,
- Original Message -
From: Patricio Díaz G. [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Monday, December 16, 2002 12:35 AM
Subject: InnoDB table lock status
I'am working with MySQL 3.23.51-Max in a linux box and Visual Fox and
Delphi
in a WinXP box, mostly
On Thursday 12 December 2002 01:45, Jing Dai wrote:
I tried on delete cascade, it didn't work either.
First of all , if you create table as you described in your previous mail,
foreign key will not be created. You can check it with SHOW TABLE STATUS.
Why? Because you specify
.. FOREIGN
At 15:12 -0800 12/11/02, Jing Dai wrote:
After install mysql-max 3.23.52 and enable innodb setting in /etc/my.cnf
file, recreate table, this time
show create table indicated it's innodb type, but tried update on cascade
still not working.
ON DELETE CASCADE is implemented, but ON UPDATE CASCADE
Have you looked if there is a problem with page0page.c ?
Simon
-Original Message-
From: Ervin Gerke [mailto:[EMAIL PROTECTED]]
Sent: 10 December 2002 12:07
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: InnoDB crash?
Got this one after a power failure.
My system is Redhat 7.3,
Ervin,
the assertion in page0page.c line 450 means InnoDB could not move index
records from a page to another page though it always checks that there
should be enough space. I have not seen this assertion fail before.
Did mysqld print a srack trace to the .err log? Can you send me the whole
Ervin,
- Original Message -
From: Ervin Gerke [EMAIL PROTECTED]
To: 'Heikki Tuuri' [EMAIL PROTECTED]
Sent: Tuesday, December 10, 2002 8:53 PM
Subject: RE: InnoDB crash?
Heikki,
That's all mysqld reported in err log. In fact I wasn't able to do a
check table since mysqld died
Mike,
- Original Message -
From: Mike Gohlke [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, December 07, 2002 6:44 PM
Subject: Re: Innodb row locking question
Benjamin Pflugmann wrote:
Hello.
On Fri 2002-12-06 at 10:28:23 -0600, [EMAIL PROTECTED] wrote
Hello.
On Fri 2002-12-06 at 11:46:16 -0500, [EMAIL PROTECTED] wrote:
From what I've been reading in the MySQL documentation, 3.23.43b
InnoDB features foreign key constraints, which is great! But from
the MySQL 4.1 wishlist items found here (scroll to the bottom):
Hello.
On Fri 2002-12-06 at 10:28:23 -0600, [EMAIL PROTECTED] wrote:
Heikki and all,
I've got a quick question which may be more general sql related but
since I'm using innodb tables specifically for the row locking.
The following process description is specifically designed to prevent
Benjamin Pflugmann wrote:
Hello.
On Fri 2002-12-06 at 10:28:23 -0600, [EMAIL PROTECTED] wrote:
Heikki and all,
I've got a quick question which may be more general sql related but
since I'm using innodb tables specifically for the row locking.
The following process description is
Hello.
On Sat 2002-12-07 at 10:36:00 -0600, [EMAIL PROTECTED] wrote:
[...]
Why do you repeat job_id = 111 and thread_id = 0? If you are using a
transaction seperation level of at least REPEATABLE READ (which is the
default), InnoDb assures that you always see the same rows within one
On Thu, 5 Dec 2002, Heikki Tuuri wrote:
the table definition below does not match the index records below. In the
index records one of the datetime columns seems to appear twice.
Heikki, you are right. The old definition of that MySQl table had two
columns twice. When I REgenerated the table,
On Wed, 4 Dec 2002, Heikki Tuuri wrote:
what MySQL version you are running? On what OS?
Version 3.23.53-max-nt-log on Windows Professional 2000
What does SHOW CREATE TABLE tabdocumentoconsultado; print?
I created again all the tables of the database called bdatena.
Now that the table is no
Evgeny,
- Original Message -
From: Evgeny Chuykov [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, December 05, 2002 12:28 PM
Subject: InnoDB shared lock with JOINs
Hallo.
I have this query:
SELECT table1.id
FROM table1
LEFT JOIN table2
Willie,
what MySQL version you are running? On what OS?
What does
SHOW CREATE TABLE tabdocumentoconsultado;
print?
Have you used an InnoDB version = 3.23.43 and stored characters with code
127 in the table? E.g., accent characters? The ordering of such characters
in the latin1 charset
:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 2:26 PM
To: John Bateman
Subject: Re: Innodb 'devices' / data files
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
Tony,
- Original Message -
From: ³Â ½Äþ [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Friday, November 29, 2002 8:08 AM
Subject: Innodb Hash search
hi,
I now test Mysql+innodb performance, my platform is Solarise 5.8 1G
RAM .
I use my-huge.cnf, set the
Just to contribute our anecdotal experience, we also found a 2x increase
in space required when we converted our MyISAM tables over to InnoDB.
While it was surprising, it wasn't unexpected. We just had to go buy
another 60GB of disk space (luckily we had planned for this). :)
Owen
On Wed,
On Wed, Nov 27, 2002 at 03:04:25PM -0800, Steven Roussey wrote:
Does InnoDB support ALTER TABLE ... ORDER BY ...?
No.
If it weren't for this command, we would never get the continuous
great performance we get from MySQL. And it keeps us from ever
really considering InnoDB. :(
Records in
On Wed, Nov 27, 2002 at 01:26:42PM +0100, [EMAIL PROTECTED] wrote:
Anyone knows the reason of this disk usage of innoDB (it's 2 time
bigger than myISAM)
InnoDB has larger per-record overhead (row headers and such).
--
Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo!
[EMAIL
Rafal,
the table cache size limit parameter in my.cnf affects also InnoDB. MySQL is
not aware that InnoDB does not open any files when InnoDB creates a handle
to a new table.
Hmm... I doubt that opening tables really takes much time. You can try
empirically if the table cache size has any
Jan,
- Original Message -
From: Jan Steinman [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, November 19, 2002 4:37 AM
Subject: InnoDB != FULLTEXT?
I'm interested in using InnoDB, but am loathe to give up FULLTEXT
indexing.
Anyone (Heikki?) know why this is so,
PM
To: [EMAIL PROTECTED]
Subject: Re: InnoDB != FULLTEXT?
Jan,
- Original Message -
From: Jan Steinman [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, November 19, 2002 4:37 AM
Subject: InnoDB != FULLTEXT?
I'm interested in using InnoDB, but am loathe to give up
At 10:10 +0200 11/15/02, [EMAIL PROTECTED] wrote:
Hi all,
I'm working on design step for a new application and I'm interested about
fulltext indexes. I need a safe transaction tables also.
Does Mysql support this or is a feature?
In need a SOLUTION for a fulltext search on the InnoDB table.
On Fri, 15 Nov 2002 [EMAIL PROTECTED] wrote:
} P.S. I have to take this decision very fast.
} Because I don't have time to search the mail list for this decision I need
} quick and short well explanation.
You might want to check the MySQL documentation on transactions:
Shakeel,
- Original Message -
From: Shakeel Sorathia [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Wednesday, November 13, 2002 9:39 PM
Subject: InnoDB: Error: tablespace size stored in header
Hi, we're using Innodb here and I just upped the number of datafiles
that
Heikki Tuuri wrote:
if you have on tape old images of ibdata files and ib_logfile's, you can try
crash recovery from them, possibly using innodb_force_recovery=6.
Unfortunately, as mentionned, I only have the data files on tape, no log
files.
Are the data files 'dumpable' ??
SQL
--
-Original Message-
From: Fernando Grijalba [mailto:fernando;ggtours.on.ca]
Sent: Wednesday, November 06, 2002 11:41 AM
To: MySQL Help
Subject: InnoDB row level locking?
In the documentation it says that InnoDB supports row level
locking. How
can I ensure that rows are locked using ADO
Michael,
- Original Message -
From: Michael T. Babcock [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, November 07, 2002 4:36 PM
Subject: Re: InnoDB recovery
Heikki Tuuri wrote:
if you have on tape old images of ibdata files and ib_logfile's
Heikki Tuuri wrote:
log files are as important a part of a database as ibdata files.
Trust me, I know; they didn't get backed up I've realized too late
though ...
You can try using some dummy log files from another installation and set
force recovery to 6 to skip the log scan.
... what's
Michael,
- Original Message -
From: Michael T. Babcock [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, November 05, 2002 6:00 PM
Subject: InnoDB recovery
I have a table that accidentally had a query run on it that NULL'd a
certain field of the entire table. I have
At 21:36 -0600 11/5/02, Nicholas Gaugler wrote:
I want to alleviate some activity from my drives by changing the
group_home_dir arch_dir variables for Innodb to a ram disk drive,
/dev/shm/. Other than loosing all transactions that were taking place
during a box crash, are there any problems
Peter,
InnoDB does not allow the index name to be specified in a foreign key
constraint:
The syntax of a foreign key constraint definition in InnoDB:
[CONSTRAINT symbol] FOREIGN KEY (index_col_name, ...)
REFERENCES table_name (index_col_name, ...)
[ON DELETE
Mysql
Greetings. I'm doing some tests using innodb for the
first time and last night, during a storm, our
energy system fall, the ups couldn't help. This
happened when we have a substancial number of
connections to the database. When the energy came
back, we realised that the database was
Edouard, you have a foreign key referencing a column in its own table.
PB
-
- Original Message -
From: Serdioukov Edouard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 29, 2002 3:23 AM
Subject: InnoDB, Foreign Key
Hello
I use Linux Red Hat 7.3 and MySQL-max
From: Heikki Tuuri
To: Serdioukov Edouard
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 29, 2002 7:23 PM
Subject: Re: InnoDB, Foreign Key
Edouard,
I tested this on Linux using mysql-max-3.23.51, the .tar.gz distro. It
worked ok.
Are you sure you were using 3.23.51? Starting from 3.23.50, InnoDB
stored? Why isn't this done automatically as it is for [ISAM] tables?
As for the why, I'm not a MySQL developer, but I believe the reason
goes something like this: When ISAM tables were implemented, they did
it the wrong way. When other table types came along, they fixed
this bug and do it the
stored? Why isn't this done automatically as it is for [ISAM] tables?
As for the why, I'm not a MySQL developer, but I believe the reason
goes something like this: When ISAM tables were implemented, they did
it the wrong way. When other table types came along, they fixed
this bug and do it
ok ... that's right for data (insert into ...) ... but
i get the error before ... when mysql try to create
child table:
CREATE TABLE ... idParent BIGINT, INDEX idpar_ind
(idParent), FOREIGN KEY (idParent) REFERENCES
parent(id)
.. when mysql parses the foreign key, parent table
doesn't exist yet!
Natale,
Friday, October 25, 2002, 10:08:00 AM, you wrote:
NB ok ... that's right for data (insert into ...) ... but
NB i get the error before ... when mysql try to create
NB child table:
NB CREATE TABLE ... idParent BIGINT, INDEX idpar_ind
NB (idParent), FOREIGN KEY (idParent) REFERENCES
NB
i tried it ... but nothing to do!
when mysql parse the foreign key in the create table i
get the error.
perhaps i'm wronging in restoring tables/db!
i use this method:
shell mysql -u user -ppassword dump file
is it wrong?
thanks.
Natale Babbo
--- Victoria Reznichenko
[EMAIL PROTECTED] ha
Natale,
Friday, October 25, 2002, 1:44:19 PM, you wrote:
NB i tried it ... but nothing to do!
NB when mysql parse the foreign key in the create table i
NB get the error.
NB perhaps i'm wronging in restoring tables/db!
NB i use this method:
shell mysql -u user -ppassword dump file
NB is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 25 October 2002 14:50, Natale Babbo wrote:
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
I would assume you will get an error: table space
My guess is that you can not operate the db when space is required and you
get error message. Like when trying to alter a table it will tell you that
the table is full. This is because MySQL will create a temporary table drop
the original and rename the new one.
HTH
JFernando
-Original
At 12:44 +0200 10/25/02, Natale Babbo wrote:
i tried it ... but nothing to do!
when mysql parse the foreign key in the create table i
get the error.
perhaps i'm wronging in restoring tables/db!
i use this method:
shell mysql -u user -ppassword dump file
is it wrong?
Depends.
- DId you add
Dobrý den,
sexta-feira, 25 de outubro de 2002, 14:26:05, napsal jste:
CB sql, query (*sigh*, I hate this filter)
CB I have an auto_increment key set up on my InnoDB table.
CB Whenever I delete all the records, the number isn't reset.
CB However, for my ISAM tables, whenever I delete all the
CB
CB However, for my ISAM tables, whenever I delete all the
CB records, the auto_increment number is reset.
CB Is there a reason for this in InnoDB? Is there a way that I
CB can reset the auto_increment number when all the records
CB are deleted?
try exec this query:
alter table TABLE_NAME
At 11:26 -0500 10/25/02, Chris Boget wrote:
sql, query (*sigh*, I hate this filter)
I have an auto_increment key set up on my InnoDB table.
Whenever I delete all the records, the number isn't reset.
However, for my ISAM tables, whenever I delete all the
records, the auto_increment number is
At 14:50 +0200 10/25/02, Natale Babbo wrote:
innodb_data_file_path=ibdata1:100M:autoextended:max:200M
anyone knows what happen if the above innodb
tablespace reach the limit of 200M?
It stops getting bigger. :-)
What do you mean by what happen? That is, what are the conditions
for which you
Natale,
Thursday, October 24, 2002, 10:57:00 AM, you wrote:
NB Anyone knows how to backup innodb tables in the right
NB sql order?
NB ... i mean ... to allow restoring correctly
NB without foreign key constraint violation (if in the
NB backup file ddl code for the child table is before ddl
NB
... can someone add InnoDB to the list of keywords?? SQL ... QUERY ...
Victoria Reznichenko wrote:
You can set up SET FOREIGN_KEY_CHECKS=0, in this case foreign key
constraints will not be checked. It's supported since 3.23.52 and
4.0.3
Out of curiousity, are the foreign key constraints
I have now ReadTheFineManual ;-) and learned that I can use
autoextend and create a new innodb-data file by changing my.cnf and
restart mysql. I've also done just that with success, now I have an
autoextend database file and two static ones.
Is there any simple way to monitor the free space of my
Heikki Tuuri wrote:
Walt,
- Original Message -
From: walt [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, October 12, 2002 11:20 AM
Subject: innodb not using correct index
Is there a way to find out what index an sql query is using? I know you
can
use
Walt,
- Original Message -
From: walt [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 15, 2002 5:56 PM
Subject: Re: innodb not using correct index
Heikki Tuuri wrote:
Walt,
- Original Message -
...
Heikki,
Thanks
On Tuesday 15 October 2002 10:59 am, Heikki Tuuri wrote:
Walt,
- Original Message -
From: walt [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 15, 2002 5:56 PM
Subject: Re: innodb not using correct index
Heikki Tuuri wrote
Lourdes,
- Original Message -
From: [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Friday, October 11, 2002 11:38 PM
Subject: InnoDB indexing questions
Hello,
I have some doubts about the index behaviour in InnoDB.
I have a table named 'Albaranes'. The definition is as
Walt,
- Original Message -
From: walt [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, October 12, 2002 11:20 AM
Subject: innodb not using correct index
Is there a way to find out what index an sql query is using? I know you
can
use explain, but those are just
Scott Pippin wrote:
I am trying to set up two data files in case the first one fills up. I
tried to use the following in my.cnf but it says there is an error. If
I take out the reference to the second data file everything works
AIX 4.3.3
MySQL 4.0.4
Hi Scott,
On Thu, 2002-10-10 at 03:28, Scott Pippin wrote:
I am trying to set up two data files in case the first one fills up. I
tried to use the following in my.cnf but it says there is an error. If
I take out the reference to the second data file everything works
AIX 4.3.3
MySQL
Jungshu,
- Original Message -
From: Heo, Jungsu [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Monday, October 07, 2002 5:49 AM
Subject: InnoDB Performance Question.
Hello everyone.
I'm working on migrating Oracle to MySQL 4.0.3
MySQL works on Redhat 7.3 and Pentium
Hi,
I was just wondering. Is it a common issue to have problems with INSERTS or
UPDATES that have not been commited stick(not commit ) even though the
connection gets killed? The thing is autocommit is on. But I still am
getting this kind of behavior from scripts that are not persistent.
I
Wayne,
please send me the whole MySQL error log.
Looks like some thread, which had reserved the InnoDB 'kernel' mutex to
access the InnoDB lock table, got stuck.
This is interesting:
5 queries inside InnoDB, 0 queries in queue; main thread: doing background
drop tables
If you drop a table
, ... output truncated!\n);
+
return;
}
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 03, 2002 9:09 PM
Subject: Re: InnoDB hard lockup
Wayne,
please send me the whole MySQL error log.
Looks like some thread, which had
.
regards,
IOD
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on inserts
(using
Iod,
- Original Message -
From: iod iod [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, September 26, 2002 8:14 AM
Subject: InnoDB AUTO-INC lock timeouts
wait for trx %lu ends\n,
- Original Message -
From: iod iod [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, October 01, 2002 11:10 AM
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on inserts (using
Thank you for your response.
We tried your example here
)
-
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
Date: Tue, 1 Oct 2002 15:00:37 +0300
To: \iod iod\ [EMAIL PROTECTED]
Subject: Re: InnoDB AUTO-INC lock timeouts / deadlocks on inserts (using
IOD,
thank you for the bug report. I was able to repeat the problem with you
scripts. The bug
Iod,
- Original Message -
From: iod iod [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, September 26, 2002 8:14 AM
Subject: InnoDB AUTO-INC lock timeouts / deadlocks on inserts (using
We have been using InnoDB with MySQL (MySQL-Max-3.23.52-1) for transaction
Hi!
Could you send me the file /mysql/sql/ha_innodb.cc so that I could check
what assertion fails in your snapshot of the source tree?
Thank you,
Heikki
Innobase Oy
- Original Message -
From: [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, September 26, 2002 12:37
On Wed, Sep 25, 2002 at 09:43:13PM +0300, Heikki Tuuri wrote:
Jocelyn,
below the latest patch which puts the code as it was in 4.0.3. Some LIKE
'abc%' ... DESC queries may return wrong results, but this is the best we
can get to 4.0.4.
I have to ask Monty about the use of
PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 8:39 PM
Subject: Re: InnoDB: Assertion failure in file ha_innodb.cc line 2180...
Jeremy,
- Original Message -
From: Jeremy Zawodny [EMAIL PROTECTED
Fournier [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 8:53 PM
Subject: Re: InnoDB: Assertion failure in file ha_innodb.cc line 2180...
Heikki
Jocelyn,
- Original Message -
From: Jocelyn Fournier [EMAIL PROTECTED]
To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 9:53 PM
Subject: Re: InnoDB
PROTECTED]
To: Jocelyn Fournier [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, September 26, 2002 9:28 PM
Subject: Re: InnoDB: Assertion failure in file ha_innodb.cc line 2180...
Jocelyn
Hi Jeremy,
Same problem for me, I submitted a bug report with a repeatable testcase
yesterday to the bugs list.
Reading the source code and changeset 1.1287, it appears this part of the
source code should be desactivated ?
(ChangeSet
1.1287 02/09/15 02:23:53 [EMAIL PROTECTED] +2 -0
Jeremy, Jocelyn,
can you try the following this patch?
The flag which bans MySQL using a descending cursor to calculate
column LIKE 'jhghj%' ORDER BY column DESC
queries was apparently put to the wrong place in ha_innodb.h. The assertion
I had added to 4.0.4 revealed this hidden bug.
The
On Wed, Sep 25, 2002 at 08:09:08PM +0300, Heikki Tuuri wrote:
Jeremy, Jocelyn,
can you try the following this patch?
I'm building a new binary row.
The flag which bans MySQL using a descending cursor to calculate
column LIKE 'jhghj%' ORDER BY column DESC
queries was apparently put to
1101 - 1200 of 1574 matches
Mail list logo
