>I'm experiencing very strange innodb behavior.
>
> What version of mysqld?
>
About test system. FreeBSD 4.2, MySQL 3.23.49, my.cnf innodb settings:
===
# Uncomment the following if you are using Innobase tables
innodb_data_file_path = ibdata1:2M
innodb_data_home_dir = /db/m
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
(http://www.ezmlm.org)
From: "gbu" <[EMAIL PROTECTED]>
I'm experiencing very strange innodb behavior.
What version of mysqld?
-
Before posting, please check:
ht
]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, September 24, 2002 12:56 AM
Subject: Mysql/Innodb bug
>
> Appears to be a database memory corruption problem. The binlog filename
> had been trashed. Eventually,
> mysql/innodb blew up trying to do a malloc.
>
> We were
Appears to be a database memory corruption problem. The binlog filename
had been trashed. Eventually,
mysql/innodb blew up trying to do a malloc.
We were accidentally running two copies of ibbackup at the same time at
around 6pm on 9/21 and 9/22.
We were accidentally running a third copy at ar
Hi
I'm experiencing very strange innodb behavior. I'm testing the following DB
structure: stn|dt|par1|par2|par3 , where stn is 1 to N, dt 1 to M, par1,
par2, par3, par4, par5, par6 are any values and stn+dt is a primary key.
So create statement looks like
CREATE TABLE t3 (stn SMALLINT UNSIGNED NO
ame_zero)
>+ block = buf_pool_get_nth_block(buf_pool, ((ulint)(ptr - frame_zero))
> >> UNIV_PAGE_SIZE_SHIFT);
> ut_a(block >= buf_pool->blocks);
> ut_a(block < buf_pool->blocks + buf_pool->max_size);
>
>- Original Message -
>From: "Heikki Tuuri
sage -
From: "Shakeel Sorathia" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, June 26, 2002 1:19 AM
Subject: innodb bug
> I've been having a problem with innodb lately. We just upgraded one of
> our machine to have 4 GB of ram in it. However, w
the swap file or
>InnoDB: ulimits of your operating system.
>InnoDB: On FreeBSD check you have compiled the OS with
>InnoDB: a big enough maximum process size.
>020625 15:40:37 mysqld ended
>============
>
>
>-Original Message-
>From:
CTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 26, 2002 4:42 PM
Subject: Re: innodb bug
> Shakeel,
>
> this may be something with 32-bit unsigned integer / signed integer
> arithmetic. I assume mysqld runs in the 32-bit mode?
>
> Are you able to compile mysqld
2310548 bytes of
>> InnoDB: memory with malloc! Total allocated memory
>> InnoDB: by InnoDB 334012166 bytes. Operating system errno: 11
>> InnoDB: Cannot continue operation!
>> InnoDB: Check if you should increase the swap file or
>> InnoDB: ulimits of your operating system.
>&
EMAIL PROTECTED]
Subject: innodb bug
I've been having a problem with innodb lately. We just upgraded one of
our machine to have 4 GB of ram in it. However, whenever I make the
innodb_buffer_pool_size greater then 2048M It crashes with the
following in the error log. It's 3.23.
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
Downloaded latest version of MySQL for Win95 (3.23.38-win) on May 21st.
After "mysqld" command this is the response:
C:\>cd mysql|cd bin|mysqld
Innobase: Assertion failure in thread 4293273545 in file M:\mysql-3.23\innobase\
os\os0file.c line 187
Innobase: we intentionally generate a memory trap.
16 matches
Mail list logo
