As for InnoDB compression -- we don't support InnoDB yet, so that's out.  Also, it looks like it compresses indexes and all of that, too -- probably *not* what we want, since we'll be accessing at least the logid index quite frequently.  TOAST looks like it might reduce or eliminate the need to put gzipped data in the DB.

However, `compressLog` will not only apply gzip, but will re-allocate the log lines into maximally sized chunks.  For the common case of a slow build with one line coming in every few seconds, we'll end up with thousands of one-line log chunks in the db.  Spread across thousands of builds, that adds up to a lot of rows in the db.  So I'd still like to do a pass over each logfile after it's finished.  But maybe that will be `optimizeLog` instead of `compressLog`.  We'll see how DB's perform, and I'll consult with some DBAs.