|
From: Tanstaafl <tan...@li...> - 2012-01-13 13:26:33
|
On 2012-01-13 8:14 AM, David Goodwin <da...@co...> wrote: > On 13 Jan 2012, at 13:05, Tanstaafl wrote: >> Hmmm... I didn't know of that limitation with InnoDB, I just read >> somewhere that InooDB was preferred… > InnoDB is good for tables which have frequent updates and reads. When > you update a MyISAM table the entire table is locked - so on a > high traffic site reads are delayed. > > I'd be surprised if there were many Postfixadmin installations which > have enough write and read traffic for it to matter which they use. > > InnoDB is the way forward - MySQL 6(?) will (perhaps does already?) > effectively default to using it. I think it recovers better from crashes > and supports transactions etc. Postfixadmin doesn't use transactions. Ok, sounds like switching to InnoDB would be the way to go then. Out of curiosity, is that what you use? Or do you use postgresql? >> Last... what is *recommended* for postfixadmin? > If it's working, don't "fix" it….. Normally I'd agree, but my reason for considering doing this switch is to 'future-proof' my postfixadmin system, and everything I've read says that utf8 is the future... gentoo has switched to utf8 for their entire systems. On the wiki page I linked in my last email, it says: "Be careful when switching to UTF-8. Once you have converted your data, any program/webapp that uses the database will have to check that the data they are sending to the database is valid UTF-8. If it isn't then MySQL will silently truncate the data after the invalid part, which can cause all sorts of problems. If your program/webapp doesn't specifically say that it supports unicode then you may want to stick with latin1 instead." So, does postfixadmin validate input for utf8 if it is used? Or is there any other reason it might be a problem? Thanks again David... |
