Re: Table compression with write (append) support

2007-05-28 Thread Yves Goergen
On 28.05.2007 18:34 CE(S)T, Kevin Hunter wrote: > At 5:45a -0400 on 28 May 2007, Yves Goergen wrote: >> Also, URLs sometimes contain things like >> session IDs. They're probably not of interest for my use but it's not >> always easy to detect them for removal. > > Really? Why wouldn't it be easy

Re: Table compression with write (append) support

2007-05-28 Thread Kevin Hunter
At 5:45a -0400 on 28 May 2007, Yves Goergen wrote: > On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote: > >> In particular, I imagine a lot of the HTTP requests would be the >> same, so you could create a table to store the requested URLs, and >> then have a second table with the timestamp and foreign

Re: Table compression with write (append) support

2007-05-28 Thread Baron Schwartz
Yves Goergen wrote: On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote: At 12:31a -0400 on 28 May 2007, Dan Nelson wrote: You want the ARCHIVE storage engine. http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html Hm, it doesn't support deleting rows and it cannot use indexes. So doi

Re: Table compression with write (append) support

2007-05-28 Thread Yves Goergen
On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote: > At 12:31a -0400 on 28 May 2007, Dan Nelson wrote: >> You want the ARCHIVE storage engine. >> >> http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html Hm, it doesn't support deleting rows and it cannot use indexes. So doing statistics o

Re: Table compression with write (append) support

2007-05-28 Thread Kevin Hunter
At 12:31a -0400 on 28 May 2007, Dan Nelson wrote: > In the last episode (May 27), Yves Goergen said: >> I'm thinking about using a MySQL table to store an Apache access log >> and do statistics on it. Currently all access log files are stored as >> files and compressed by day. Older log files are c

Re: Table compression with write (append) support

2007-05-27 Thread Dan Nelson
In the last episode (May 27), Yves Goergen said: > I'm thinking about using a MySQL table to store an Apache access log > and do statistics on it. Currently all access log files are stored as > files and compressed by day. Older log files are compressed by month, > with bzip2. This gives a very goo

Table compression with write (append) support

2007-05-27 Thread Yves Goergen
Hi, I'm thinking about using a MySQL table to store an Apache access log and do statistics on it. Currently all access log files are stored as files and compressed by day. Older log files are compressed by month, with bzip2. This gives a very good compression ratio, since there's a lot of repetiti