myisampack / myisamchk Problem

Hello * my Problem (resolved for newer mysql Versions): A MyIsam Table is packed with myisampack A subsequent myisamchk -r or -o with index reordering erroneously marks wrong indices in the packed table for 4.0.15 (unpacking reconstructs the original table) This seems to be a known issue

MERGE Table Problem

Hello * reproducable Problem: Content of UNION: logs_20040608,logs_20040609,logs_20040611,logs_20040612,logs_20040613,logs_20040614, logs_20040615 results: 0E0 DBD::mysql::db do failed: Can't open file: '#sql-13c1_12.MRG'. (errno: 144) at /usr/local/sbin/new_MERGE_table.pl line 276. Unable to

Problem with Merge Table,ERROR 1016: Can't open file: '#sql-407f_f.MRG'. (errno: 144)

Hello *, a) what could be reason /solution for the following Problem: ERROR 1016: Can't open file: '#sql-407f_f.MRG'. (errno: 144) b) in which directory the below reported intermediate file should be generated mysql use syslog Database changed mysql ALTER TABLE logs UNION=(

myisampack, check: already compressed ?

Hello * Question: Is there a (cheap) way to find out if a MyISAM Table is already compressed, before running a myisampack on it ? Goal: -In a script that regularly compresses Tables i'd like to check before packing. In case the script has previously been started and already done the

merge tables for big log files ?

Hello *, goal: using merge tables for annual / monthly storage of syslog information using php-syslog-ng and syslog-ng problem: -one actual table must be available for inserts -the merge table needs to be the target for reports and queries -static parts of the merge table should be