Re: Tuning MySQL 4.0.20 for large full table scans

2004-06-03 Thread Matt W
Hi Dan, - Original Message - From: "Dan Nelson" Sent: Thursday, June 03, 2004 12:34 PM Subject: Re: Tuning MySQL 4.0.20 for large full table scans [snip] > > Not sure what can be done about making it not go straight to tmpdir > > with a BLOB column in the

Re: Tuning MySQL 4.0.20 for large full table scans

2004-06-03 Thread Dan Nelson
In the last episode (Jun 03), Dossy said: > On 2004.06.03, Dan Nelson <[EMAIL PROTECTED]> wrote: > > Consider multicolumn indexes; if you always "SELECT field1 from > > table where field2=blah", creating an index on (field2,field1) will > > let mysql bypass table lookups completely. > > Our typica

Re: Tuning MySQL 4.0.20 for large full table scans

2004-06-03 Thread Dossy
On 2004.06.03, Dan Nelson <[EMAIL PROTECTED]> wrote: > > Consider multicolumn indexes; if you always "SELECT field1 from table > where field2=blah", creating an index on (field2,field1) will let mysql > bypass table lookups completely. Our typical queries look something like: SELECT level1, le

Re: Tuning MySQL 4.0.20 for large full table scans

2004-06-03 Thread Dan Nelson
In the last episode (Jun 03), Dossy said: > The schema in question needs a redesign (dynamic row format, contains > two BLOB columns) but I was wondering if anyone has written up some > guidelines for general data warehouse configuration of MySQL 4.0 -- > Google has not turned up anything useful. >