On Tue, 2007-06-05 at 11:22 +1000, Jake Anderson wrote: > Paul J Stevens wrote:
> > Fully backward compatible: just add two tables like I stated. Using sha1 > > over > > the whole of the file, fall back to old-style storage if new-style not > > available. I guess the one doing the work gets to make the decisions... > > > > > I wonder if keeping the old style stuff around would be worth it? > It seems a wasteful performance hit that is only really needed during > the transition. > My vote is to make the new stuff "the way" and take the downtime hit. > With any luck the change should be pretty stable and be around for quite > a while. I would prefer not to force people through these annual migration headaches. Anything that can be made piecemeal should be. > > In this new setup; simple rfc2822 messages are stored in a single block. > > Yes: no > > more chopping off of the headers. For multi-part messages, the first block > > contains the rfc headers plus the mime-preamble. Following blocks contain > > the > > mime-parts as-is. > > > Do you convert them from whatever encoding they are in back into a raw > binary before storing them? My understanding is the encoding adds > significantly to the size of the files over the wire. I think we should keep things encoded, because that's what clients expect to receive. OTOH, encoded data cannot be searched. Aaron _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
