•Re: Big hairy ugly log sorting merging problem

This is all screaming "use a real database". Even DBD::SQLite will help tremendously, provided you index the proper columns. But if you want something fancier, I strongly suggest PostgreSQL, which is "Oracle without the price or trouble".

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Comment on •Re: Big hairy ugly log sorting merging problem

Replies are listed 'Best First'.
Re^2: Big hairy ugly log sorting merging problem by mr. jaggers (Sexton) on Aug 07, 2004 at 01:45 UTC
Ok, good idea. I wasn't thinking along the lines of columns, but that's exactly what they are... plus MySQL and DBI, et. al, are already on the log-file-containing-machine. It's no postgres, but it should do for this, I think. I think the real sort problem is the resolution of the timestamp in our combined log format. Does anyone (that cares) happen to know if Apache will do finer grained log timestamping than single seconds?	[reply]
Re^3: Big hairy ugly log sorting merging problem by Aristotle (Chancellor) on Aug 07, 2004 at 01:48 UTC
You just need to define the log format appropriatey. See the mod_log_config documentation. Makeshifts last the longest.	[reply]
Re^4: Big hairy ugly log sorting merging problem by mr. jaggers (Sexton) on Aug 07, 2004 at 02:23 UTC
Ok, so then "no", since strftime won't go smaller than one second... cool, thanks for digging up the doc! I should have done that. sigh why can't we all just agree on reporting all time in clock cycles since the epoch (with a architecture specific tick-per-second scalar for the whiners and complainers)?	[reply]