Hi! The optimizer issue is a known bug in 4.0.16 (I think). It should be resolved soon if my memory of the traffic on the list as of late is accurate.
Regarding the issue with threads on Redhat 9.0 - did MySQL 4.0.13-Max come with Redhat 9.0 (or was it supplied by Redhat)? If it was, then chances are it used the NPTL library which provides "proper" POSIX thread semantics, meaning that all threads in a process share the same PID and thus don't show up individually in top or other process monitoring/auditing programs. If you downloaded 4.0.16 from anywhere else, it will have been linked against the LinuxThreads library, which uses the clone() system call to create new threads, resulting in each thread having a unique PID and being visible in top. Hope this helps! Regards, Chris On Mon, 2003-12-15 at 13:54, trevor%tribenetwork.com wrote: > Hello, > > > > I recently upgraded from 4.0.13-max to 4.0.16 and now the same > queries/sec cause a higher load on the database server. I upgraded to > 4.01.6 since the optimizer was not using some of my fulltext indicies. All > our tables are MyIsam so I figure there is no reason to use the MAX version. > In addition my Redhat 9.0 machine now lists all the mysld threads under top, > whereas before top listied a single myslqd process. Any information is > appreciated. > > > > Thanks, > > > > Trevor > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
