Simon wrote:
I have read various things, but it would be good to get the correct
thing todo here please?
First check your database settings. Default collation was latin/swedish
for mysql I think. Compare your old and new my.cnf files. Check the
client as well as the mysql subsections. Has
Aleksander Kamenik wrote:
Simon wrote:
I have read various things, but it would be good to get the correct
thing todo here please?
First check your database settings. Default collation was latin/swedish
for mysql I think. Compare your old and new my.cnf files. Check the
client as well
On Thu, Mar 12, 2009 at 7:27 AM, Paul J Stevens p...@nfg.nl wrote:
Aleksander Kamenik wrote:
Simon wrote:
I have read various things, but it would be good to get the correct
thing todo here please?
First check your database settings. Default collation was latin/swedish
for mysql I think.
Paul J Stevens wrote:
Actually, 5.1.32 was released last week which was pitched as production
quality. Personally, I'll stick with Monty's advice: avoid 5.1:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
Has anybody compared the performance of
Hi There,
Our dbmail 2.0 running on debian sarge was damaged last night.
We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql database from the old server is just being recovered
onto the new server... once completed, is this just simply a matter of
running the
On Wed, Mar 11, 2009 at 12:44 PM, Simon grem...@gmail.com wrote:
Hi There,
Our dbmail 2.0 running on debian sarge was damaged last night.
We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql database from the old server is just being recovered
onto the new
On Wed, 11 Mar 2009 12:46:07 +1300, Simon grem...@gmail.com wrote:
On Wed, Mar 11, 2009 at 12:44 PM, Simon grem...@gmail.com wrote:
Hi There,
Our dbmail 2.0 running on debian sarge was damaged last night.
We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql
On Wed, Mar 11, 2009 at 1:07 PM, Aaron Stone aa...@serendipity.cx wrote:
Our dbmail 2.0 running on debian sarge was damaged last night.
We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql database from the old server is just being recovered
onto the new
On Wed, 11 Mar 2009 13:14:58 +1300, Simon grem...@gmail.com wrote:
On Wed, Mar 11, 2009 at 1:07 PM, Aaron Stone aa...@serendipity.cx
wrote:
Our dbmail 2.0 running on debian sarge was damaged last night.
We are currently building a new VM with debian etch and dbmail 2.2.
The innodb mysql
On Wed, Mar 11, 2009 at 1:26 PM, Aaron Stone aa...@serendipity.cx wrote:
I'm sure it will! Be sure to keep a backup of the restored database in
pre-2.2 script state, just in case, of course. If you could report back to
the list how long the two steps take (sql migration and dbmail-util) that
On Wed, Mar 11, 2009 at 1:26 PM, Aaron Stone aa...@serendipity.cx wrote:
Thanks Aaron, The VM has 2 x E5310 Xeon Cores @ 1.6GHz... and the
ibdata1 file is approx 40GB.. so that upgrade script might take a
while huh?
I'm sure it will! Be sure to keep a backup of the restored database in
11 matches
Mail list logo
