performance for large transactions I would get by further increasing the buffer pool
size...
Thanks again,
Sergei
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 15, 2004 2:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Expensive InnoDB queries crash mysql daemon
ei Skarupo"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, July 15, 2004 9:37 AM
Subject: RE: Expensive InnoDB queries crash mysql daemon
> Thanks for your reply.
>
> I think on this machine MySQL was installed from an RPM distribution... =
> All
uot;" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, July 15, 2004 1:50 AM
Subject: Expensive InnoDB queries crash mysql daemon
> --_=_NextPart_001_01C469F5.1B46DF30
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding:
yodbc
Sent: Thursday, July 15, 2004 1:50 AM
Subject: Expensive InnoDB queries crash mysql daemon
> --_=_NextPart_001_01C469F5.1B46DF30
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hello All,
> =20
>
Hello All,
I hope someone can shed some light on this problem...
This concerns large InnoDB tables (having on the order of millions of rows).
When I run ALTER TABLE (for example, to change the default column value) or UPDATE or
DELETE queries that affect many rows, mysqld-max crashes and app
