Hi!
Nowadays we've conducted something what I can call extended testing of
MySQL on Solaris10/x86.
The most annoying issue is a problem with locking queries to MyISAM-type
tables.
Mechanism seems to be simple to explain - long running query locks table
for READ, next there is some DML query wh
Heikki Tuuri wrote:
Carl,
InnoDB does purge deleted rows from the ibdata files. Certain
PostgreSQL advocates have been spreading a claim that InnoDB would not
do that, but the claim is false.
Could You explain more about reusing space previously taken by deleted
rows? Is this concept simil
Viktor Fougstedt wrote:
Hi, and thank you both for valuable tips.
The MySQLd in question runs on a mailserver, and a large amount of
processes (Postfix, Maildrop and Squirrelmail) connect to it, run one
or two simple queries, and then disconnects.
There is only one client that is constan
Hi!
While ago we perform in our company short experiment in the framework of
mysql tests.
One of our databases is mysql-4.0.15 on i386 Linux. It is MyISAM-based.
Traffic on it consists of mix of selects (quite big share of count
aggregates) and dml operations with quite high share of the latter
Gleb Paharenko wrote:
Hello.
Maybe the output of innodb_monitor won't be truncated.
Create the innodb_monitor table and check if you see
the full output in the .err log. See:
http://dev.mysql.com/doc/mysql/en/innodb-monitor.html
this helps - thanks
--
MySQL General Mailing List
Ady Wicaksono wrote:
You should try
*SHOW INNODB STATUS \G;*
Remigiusz Soko?owski wrote:
Hi!
problem is not critical, however it would be nice to get some workaround
from time to time I check innodb status - the most interesting
sections, I believe, are:
FILE I/O, INSERT BUFFER AND ADAPTIV
Hi!
problem is not critical, however it would be nice to get some workaround
from time to time I check innodb status - the most interesting sections,
I believe, are:
FILE I/O, INSERT BUFFER AND ADAPTIVE HASH INDEX, LOG, BUFFER POOL AND
MEMORY and ROW OPERATIONS
unfortunately they are at the bo
let's say that we have the following settings:
Variable_name: query_cache_limit Value: 64kB
Variable_name: query_cache_size Value: 4MB
and status:
| Qcache_queries_in_cache| 1679 |
| Qcache_inserts| 2242534|
| Qcache_hits | 1058592
Gleb Paharenko wrote:
Hello.
Use skip-innodb, this should prevent MySQL from InnoDB initialization.
Remigiusz Soko$owski <[EMAIL PROTECTED]> wrote:
Hello!
Do You know if myISAM-specific settings have any impact on database
performance,
if the only MyISAM database is my
Hello!
Do You know if myISAM-specific settings have any impact on database
performance,
if the only MyISAM database is mysql?
I know that there are some default settings and I wonder if for example
memory buffers are allocated even if they are not used? Is it necessary
to disable those setting
Hi!
last night we try to upgrade from 4.0.15 to 4.0.24. We thought, that it
is possible without dumping data. We upgrade only server (clients were
still 4.0.15). In changelogs in versions higher than 4.0.15 there were
no info about some incompatible changes and those bound with InnoDB were
conn
Hi!
I wonder if there is any possibility to switch log off on running server?
Usually I have here general logs disabled due to performance and space
saving reasons - but of course sometimes it is needed to find out full
info about queries executed. It'd be fine to have possibility to run
server
matt ryan wrote:
Tobias Asplund wrote:
<>On Tue, 7 Sep 2004, matt ryan wrote:
I forgot, did you have multiple slaves on multiple machines? If so,
do they
have identical hardware/drivers?
Multiple slaves on same machine, one works fine
Do You tried to distribute replication to other machines? Is
matt ryan wrote:
The table is 9 gig, and the index is 8 gig
unfortunately the primary unique key is almost every column, if I were
to make it one using concat, it would be huge.
I tried making those fields a hash, but it did not work, I had
duplicate hashes for non duplicate records!!
Matt
If I
14 matches
Mail list logo
