Well, first thing I'd do, is symlink the log table files onto a separate set of spindles. No use bogging the main data spindles down with logwrites.
On Tue, Apr 20, 2010 at 5:33 PM, Carsten Pedersen <cars...@bitbybit.dk>wrote: > Carsten Pedersen skrev: > > Jim Lyons skrev: >> >>> Has anyone tried using the log_output option in mysql 5.1 to have the >>> general log put into a table and not a flat file? I used it for a while >>> before having to downgrade back to 5.0 but thought it was a great idea. >>> I'm >>> curious to see if anyone feels it helps analysis. >>> >> >> I tried that once, and ran into some problems. Depending on your exact >> version, you might experience the same. >> >> http://www.bitbybit.dk/carsten/blog/?p=115 >> >> (also has a number of good comments on analysis tools) >> >> And yes, having the data available in a table is a Good Thing for >> analysis. >> >> / Carsten >> > > Minor correction: The post i point to is about the slow log, but I presume > also relevant for the general log. And the good comments I mentioned come in > the followup posting at http://www.bitbybit.dk/carsten/blog/?p=116 > > / Carsten > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=vegiv...@tuxera.be > > -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
