Ian G Batten wrote: > I understand some of the technical, philosophical and historical > reasons why this isn't the case, but every now and again I find myself > wishing that Cyrus had an SQL backend for the various databases > (perhaps not delivery, because losing it isn't the end of the world, > but certainly for mailboxes). > > In our case, we have really big Oracle and Postgres systems that could > proably handle the load imposed by out mailsystem metadata as well as > our mailsystem copes with it itself via skiplist, but we would could > then manage those databases with the same tools we use for the > production systems (hot backups, replication, etc). > > Losing the mailboxes database can spoil your whole day, and the > lengths we go to to keep it safe (snapshots of the filesystem, hourly > runs of ctl_mboxlist -d, etc, etc should really be necessary if it > were in a production SQL database. > > In my copious spare time, I might take a pass at the cope and see how > hard it looks. So you don't duplicate his effort, I should mention that Ken Murchison already wrote a generic SQL backend for Cyrus. We've done a small amount of testing with sqlite, but there's still some work to be done before it's production-ready. Thanks, Dave ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
