There is a MySQl/Innodb bug with Mysql-Max 4.0.17
on mac osx 10.3 panther. A google search showed
a similar problem with another platform (I think
it was windows).
I am running 4.0.14 without any problems. After
upgrading to 4.0.17, copying the data directory
from 4.0.14 to 4.0.17 and then startin
mysql.com/doc/en/ORDER_BY_optimisation.html
* http://www.mysql.com/doc/en/Change_column_order.html
This was an automated response to your email 'BUG: InnoDB ORDER BY DESC may hang in
4.0.10'.
Final search keyword used to query the manual was 'BUG: InnoDB ORDER BY DESC may hang
4.0.1
Hi!
A rather serious bug was introduced to 4.0.10 in connection of another bug
fix.
If you have a composite key (col1, col2) in an InnoDB table, then a query of
type
SELECT ...
FROM ...
WHERE col1 = x ORDER BY col2 DESC;
may hang in an infinite loop.
The fix is in 4.0.11.
Best regards,
Heikk
nobase Oy
sql query
.......
Subject: Bug? InnoDB transactions and temporary table hanging
From: Samuel Liddicott
Date: Thu, 6 Feb 2003 10:57:13 -
I came accross a problem porting our tv listings system from postgres to
mysql with InnoDB.
With InnoDB tables, read-only transactions
I came accross a problem porting our tv listings system from postgres to
mysql with InnoDB.
With InnoDB tables, read-only transactions started after a read-write
transaction touching the same rows are able to read data as it was before
the read-write transaction began; UNLESS the "read-only" trans
Hi!
A user of InnoDB Hot Backup just reported a bug. He has 3 InnoDB log files,
each 1 GB in size.
A 32-bit integer overflow can cause InnoDB to write log in a wrong offset.
That can spoil InnoDB recovery.
If you have too big log files, please follow the instructions at
http://www.innodb.com/ib
On Fri, 17 Aug 2001, Heikki Tuuri wrote:
Problem resolved, thank you very much. It was indeed my missing a
concept, description below:
> it was not immediately clear to me what your application
> does. Does one connection update the table and
> another connection do the SELECT?
Yes, as it's t
Eric,
it was not immediately clear to me what your application
does. Does one connection update the table and
another connection do the SELECT? Then the problem
might be the consistent read. I have copied below a segment
from the InnoDB manual at www.innodb.com :
When you issue a consistent
On Thu, 16 Aug 2001 16:43:22 -0700 (PDT), "Eric J. Schwertfeger" <[EMAIL PROTECTED]>
wrote:
>>The interesting part is, if I run the program with autocommit on, it
>>works fine. Unfortunately, transactions are essential. I found that the
>>program works if I turn autocommit on but wrap the criti
I've got a part of a complex system that isn't behaving as expected. I've
got one perl program running with autocommit off that creates entries in a
table and commits the changes. At some point, the rows have their state
field changed from 'active' to 'closed', and these changes are then
commit
Hi!
On Win 9x and ME you should run mysqld-max.exe.
mysqld.exe was in 3.23.38 accidentally compiled with __NT__
defined.
Regards,
Heikki Tuuri
Innobase Oy
Copied message:
LS.This is the text i sent you, the text you have seen was a attachment
C:\mysql\bin>mysqldInnobase:
LS.
This is the text i sent you, the text you have seen was a attachment
C:\mysql\bin>mysqld
Innobase: Assertion failure in thread 4294946135 in file M:
\mysql-3.23\innobase\
os\os0file.c line 187
Innobase: we intentionally generate a memory trap.
Innobase: Send a bug report to [EMAIL PROTECTED
12 matches
Mail list logo
