Bruce Dembecki wrote:
At the 2004 Users Conference in Orlando in April there were two sessions on
optimizing MySQL hosted by a MySQL staffer who's name eludes me for the
moment.
Peter Zaitsev I believe. He did some InnoDB performance tuning sessions.
He told the assembled masses that in benchmark
Hi Bruce,
On Dec 28, 2004, at 2:38 PM, Bruce Dembecki wrote:
As a person in the process of migrating from 4.0 to 4.1 and having
already
scheduled the downtime with my clients for this Friday morning, and
having
to do a full dump and import already as part of the migration process
I'd
like to kno
L and contributing to it's development.
Best Regards, Bruce
On 1/6/05 7:38 AM, "Ken Menzel" <[EMAIL PROTECTED]> wrote:
> Hi Bruce
>
>
> - Original Message -
> From: "Bruce Dembecki" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday
Hi Bruce
- Original Message -
From: "Bruce Dembecki" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 30, 2004 2:51 AM
Subject: Re: Fixing "the worst InnoDB corruption bug in 3 years" -
when
As a side note with demonstrated performance increases when using
t; <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, December 30, 2004 9:51 AM
Subject: Re: Fixing "the worst InnoDB corruption bug in 3 years" - when
Thanks Heikki, I understand the bug, and I know you fixed it, for which I
a=
m
very pleased, as always problems
sorry
--
-- -- -- --
Sayusi Ando
-- -- -- --
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Thanks Heikki, I understand the bug, and I know you fixed it, for which I am
very pleased, as always problems when identified are fixed quickly :-)
I guess the question I was trying to ask of MySQL is when will 4.1.9 be
built... It's very frustrating knowing that a problem has been fixed
(particul
ummer 2001. Fortunately, the bug affects few users, because not too many
are running with innodb_file_per_table.
Regards,
Heikki
..
List: mysql
Subject: Fixing "the worst InnoDB corruption bug in 3 years" - when
From: Bruce Dembecki
Date: 2004-12-28 22:38:36
Me
In the MySQL Manual under InnoDB in the "Using Per-Table Tablespace" section
it says clearly at the top:
NOTE: CRITICAL BUG in 4.1 if you specify innodb_file_per_table in `my.cnf'!
If you shut down mysqld, then records may disappear from the secondary
indexes of a table. See (Bug #7496) for more i
