Hello,
On Tuesday 04 February 2003 14:46, Grover Cussi N. wrote:
restore to the original size ?, I see that the tendence of the innodb
tables is to grow, and grow, and never will reduce the size, it is
posible to control this?
I had the same problem, it went on until I had 44G of InnoDB
Hey list,
Recently I tried to upgrade MySQL to a newer version. I have 3.23.53a-max
running but that is vulnarable to a bug. So I went to mysql.com and grabbed
the .54a-max binary.
First thing I noticed was the small size, only 6M while .53a was 10M.
Net thing I started .54a.. it took the load
Hey Lenz,
Can you please try a ldd /path/to/mysqld and check, if it
requires shared libraries or is a static binary?
Ok, here you go:
# ldd /usr/local/mysql-max-3.23.54a-pc-linux-i686/bin/mysqld
libdl.so.2 = /lib/libdl.so.2 (0x4002)
libpthread.so.0 = /lib/libpthread.so.0
From: Lenz Grimmer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 9:43 PM
OK, as I already assumed, the Max binary was not linked statically. Doh!
Interesting, that this also causes the load to spike, even though it's not
statically linked against an unpatched glibc.
Maybe it
-Original Message-
From: Lenz Grimmer [mailto:[EMAIL PROTECTED]]
Thanks for confirming! I will publish the binary right away. Sorry for the
trouble.
Just a small thing I noticed:
version 3.23.54-max-log
missing the 'c' in the version string ;)
- kees
Hey David,
-Original Message-
From: Lopez David E-r9374c [mailto:[EMAIL PROTECTED]]
kees
How do you measure spiked queries/s?
All I see is average queries/s from the status command.
I can see the calculation based on uptime in seconds and
total queries in that time. But that's
Hey,
Use mysqldump.
See the manual / cli help for how to do it :0
-kees
-Original Message-
From: Silmara [mailto:silmara.sami;uol.com.br]
Sent: Wednesday, October 30, 2002 5:39 PM
To: [EMAIL PROTECTED]
Subject: Backup InnoDB
How can I do backup of only one DataBase? And How
Load issue resolved. Whew! Looking forward to 4.0.5 with the same fix.
Such a relief! Thanks for all the work to resolve this!
Als here the loadissues have been resolved, I had to run .49a and had to
miss a couple of innodb features for it, but finnaly .53 works again as
stable as .49 has been
it is released. at least; it can be found on ftp.sunsite.dk
-kees
-Original Message-
From: Victoria Reznichenko [mailto:victoria.reznichenko;ensita.net]
Sent: Thursday, October 17, 2002 11:44 AM
To: [EMAIL PROTECTED]
Subject: re: when will 3.23.53a be released?
Lars,
Hello list,
I tried to install 2.23.53 (upgrade from .49a) but mysqld won't start (so i
had to put back to old .49a).
It does give a strange error messages:
./mysqld: unrecognized option `--innodb_data_home_dir='
./mysqld Ver 3.23.53-max for pc-linux-gnu on i686
This is strange imho, It is
10 matches
Mail list logo