On 10/22/2013 2:42 AM, Thomas Raschbacher wrote:
On 2013-10-21 19:54, Curtis Maurand wrote:
I see several upgrade scripts in the sql folder. I'm assuming that
since I'm on 2.2.18 I'll need to run them in order starting with
2_2-3_0.mysql? I know assumptions are a bad thing, but the docs
folder is scarce and the Wiki is equally scarce on upgrade procedures.
building of the new version was successful. upgrading is going to
take some time since the database is currently around 16G
Let me know if I'm wrong.
Thanks,
Curtis
Did you read UPGRADING yet?
Here's a link if you don't have the tarball handy:
http://git.dbmail.eu/paul/dbmail/tree/UPGRADING?h=dbmail_3_1
I read UPGRADING (didn't see it there, thank you) It still does not
outline the database change procedure other than a couple of things that
you have to do after running it. Then again, what do I know? I'm just a
dumb admin. It would be helpful to have the steps. I haven't upgraded
in a very long time. I changed from gentoo (just too difficult to keep
up with) to Ubuntu and have had lot's of trouble getting dbmail to
compile. I solved that trouble and got it to compile on 3 different
servers. I have the 2.2 version running on one of my Ubuntu machines
and the Gentoo machine (load balancing.) I need to retire the Gentoo
box. There was obviously a big change between 2.2 and 2.3 given what
I'm reading. The other piece that I noticed that was missing from the
doc is which database URI types are supported. It calls out sqlite://
in the UPGRADING, but not any others. I'm assuming that mysqli:// is
supported as well as pgsql://. I have no experience with pgsql as I've
been running mysql for a very long time. So if my pgsql:// is wrong,
someone please correct me.
I only get one chance to do this right without losing customers. email
is always touchy. I've tried in the past to set up mysql replication
for this and powerdns and have had absolutely no success, but that 's
for the mysql list. :-)
I'm hoping when all is said and done that message searches from the two
web clients I use actually work. Currently they just timeout and the
imap connection drops after 5 or 10 minutes. I'm currently on 2.2.18.
The current database size is 16GB, but may be less after running
dbmail-util -ay on the database a couple of times as it hasn't been done
in a while. bzipped backups of the database dumps run about 2.5GB.
Cheers,
Curtis
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
