[Mod_log_sql] Logging POST data and indexing

[Edward Rudd]

On Tue, 2005-05-31 at 05:25, Justin Finkelstein wrote:
> Hi guys
> 
> I've just had a look at my database and I've notice that nothing
> appears to be logged for POST requests; does this need to be
> explicitly turned on in the module?

They should be logged and are so on my servers running 1.100.  The
actual data posted does not and will not be logged. but the requested
URL will be.

> Also, I use the log_mass_virtual_hosting option, and I've noticed that
> this doesn't generate any indices on the tables - could I request an
> option for creating indices on the fly for new tables? I'd be happy to
> work on this if the project's open for other devs...

The biggest issue with adding indexes (which I believe there is a bug
report on issues.outoforder.cc about this) is which columns to index,
and worrying about the performance hit for logging, as having indexes
slows down the process of inserting data.  I plan to add back in INSERT
DELAYED for mysql in the next release which should relieve this issue
some, but that will only help MySQL back-ends.

If you are handy and knowledgeable w/ SQL index configuration and would
like to test indexes and find a *good* fast set for the table that would
help.

And I'm always open to contributions, just send the patches to this list
or attached to a bug in issues.outoforder.cc.

-- 
Edward Rudd <urkle at outoforder.cc>
Website http://www.outoforder.cc/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.outoforder.cc/pipermail/mod_log_sql/attachments/20050531/128d184c/attachment.bin