Intel ICC libs for Mysql 4.1 using libc 2.3

The Mysql download page says I need to install these libraries if I am using libc 2.3.x. I have a couple of questions: -- do I install them by just copying them to /usr/local/lib? -- will they play that silly game of running unoptimized code on AMD processors? -- Christopher L. Everett

Repeated corruption with MySQL 4.1.x using FULLTEXT indexes

afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug. -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com -- MySQL General Mailing List

Re: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes

and index references 1307000^C Also, I gt a segfault trying to use myisamchk --sort-records. Christopher L. Everett wrote: I have an application where I create a faily large table (835MB) with a fulltext index. One of our development workstations and our production server will run the script

Re: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes

Ed Lazor wrote: -Original Message- From: Christopher L. Everett [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 1:47 AM To: Mysql List Subject: Repeated corruption with MySQL 4.1.x using FULLTEXT indexes I have an application where I create a faily large table (835MB

Compiling from source

executables? I find this hard to believe when the pgcc download page at goof.com was last updated in 2000. 2. What compiler flags do the binaries distributed on www.mysql.com use? -- Christopher L. Everett Chief Technology Officer www.medbanner.com MedBanner, Inc

Re: MySQL 4.1 replication relay log control

Victoria Reznichenko wrote: relay-log-purge is available from 4.1.1. Do you use 4.1.1 or 4.1.0? Is it in the manual because relay-log-purge is available in 4.0.x? AFAICT, 4.1.1 isn't available for download from the mysql.com site. 4.1.0-alpha is. How would one obtain 4.1.1? Would this work to

MySQL 4.1 replication relay log control

The online manual at http://www.mysql.com/doc/en/Replication_Options.html says that these two variables: max-relay-log-size=# relay-log-purge=0|1 exist to control the size of the relay log. But when I try to start my slave server with: set-variable = max-relay-log-size=192MB set-variable =

ran out of space for bin logs

Aparrently my binlogs grew and grew and ate up all the space on their partition. At this point, I see this on the master mysql show master status; Empty set (0.00 sec) and this on the slave: mysql show slave status\G *** 1. row ***

Missing rows from select statements on heap table type

I upgraded from 3.23.27-beta to 3.23.32 after seeing bugfixes on intermediate versions. However the problems are continuing: Mod_perl DBI/DBD::mysql queries are failing to return rows that I know exist. It could be DBI/DBD::Mysql, but just in case I have some questions: - Are there known