[Mod_log_sql] Delayed Inserts
urkle at outoforder.cc
Tue May 6 22:40:42 EDT 2008
On May 6, 2008, at 10:34 AM, Jay Fougere wrote:
> My problem is that although I only keep 3days worth of logs in the
> database, the database files still grow to several gigabytes in size
> which is fine until I need to lock one of the tables. At this
> point, all
> of my sites are delayed because they cannot log due to a lock (whether
> it be for repair or what have you). This can take up to several
> depending on the operation involved and of course, having high-traffic
> sites down for this period is unacceptable :)
Are using myIsam? or Innodb? Innodb supports row level locking so
some operations won't lock up the whole table.
Me, personally I'm using the archive table format, which uses
SIGNIFICANTLY less storage space.
> According to the current documentation, "If you are experiencing
> which could be solved by delayed inserts, then set
> On in the httpd.conf . All regular INSERT statements are now INSERT
> DELAYED, and you should see no more blocking of the module."; However,
> LogSqlDelayedInserts seems to have been deprecated in version 1.106
> (according to the changelog) in favor of using LogSQLDBParam. I have
> read the documentation and Googled "LogSQLDBParam" but cannot find the
> proper method of enabling delayed inserts.
Unfortunately current releases of mod_log_sql do not support Delayed
inserts, and I have not yet added it back in. I will be doing so for
the next release, as I myself want this feature back in for some of
my high load servers. However it may be a few weeks before I get
another release out.
More information about the Mod_log_sql