The problem right now is that we're trying to get the 2.0 release out, and so there's basically three threads happening right now:
- Getting 2.0 released without further adieu - Thawing for a specific set of usability fixes - Random other stuff Unfortunately, your compressed messageblks thread is in that third category... I think it's a really interesting idea, and makes a lot of sense once we have the headers parsed out as there'd be no reason to search the messageblks, and indeed no reason to look at them at all unless it's the message you want. Aaron Hans Kristian Rosbach <[EMAIL PROTECTED]> said: > > Maybe it would be worth testing these.. > > 'External' seems like a good default for me and would require > > no changes to dbmail to work (except the database creation). > > If it works well, and my zlib idea is too far off base then > > 'extended' might be a good choice too, but should be made a > > install-time option to 'external'. > > I'm beginning to look like a troll now.. > > http://www.postgresql.com/docs/7.4/interactive/sql-altertable.html > Take a look at 'set storage'. > I think that means that text and varchar are 'extended' by default. > Interesting. > > I could imagine me trying to set the header field to 'external' or > even 'plain' in order to increase speed. After all, header speed > is one of my #1 priorities when it comes to webmail. But this > would require us to have separate fields for message and header, > pretty please? > > I'll try to not send any more mails unless somebody answers now.. > > -HK > > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
