It sounds similar but not exact. The bug you refer to is related to the Memory table
properties being reported incorrectly and constantly increasing during updates. The
problem I am seeing is that when tables are dropped and recreate/repopulated, or indexes
are dropped and recreated, the size of real memory being used by mysqld increases when it
should not.
I have openned a new bug on this
http://bugs.mysql.com/bug.php?id=21332
And the assigned person has requested that I try it on the latest release of 5.0 (5.0.23
vs 5.0.19). I will try this, but it would be good to know if this has been seen by
others or is a known issue.
Regards,
Bill Willits
---- Sergei Golubchik <serg@stripped> wrote:
> Hi!
>
> This looks like a http://bugs.mysql.com/bug.php?id=18160
>
> On Jul 27, bwillits@stripped wrote:
> > I am using 64bit Linux with 32Gb Ram with mysql v5.0.19. When I create
> > and load Memory tables of about 2Gb each, the size of memory used by
> > the mysqld process increases as expected. Here are the issues I am
> > having.
> >
> > 1) The rate of growth of the memory used by mysqld does not seem to be
> > in line with the size reported for the table(s) (data_length,
> > index_length). The mysqld process grows at about double the rate of
> > the memory table growth.
> >
> > 2) When I drop the memory tables, the memory used by mysqld does not
> > reduce. This means that as I drop and recreate memory tables, the
> > memory used on the server continues to grow, eventually using up all
> > available memory and causing the server to crash.
> >
> Regards,
> Sergei
>
> --
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
> /_/ /_/\_, /___/\___\_\___/ Kerpen, Germany
> <___/ www.mysql.com
