Date: Mon, 7 Jul 2008 10:21:53 -0400 From: John Almberg <jalmberg@identry.com> To: freebsd-questions@freebsd.org Subject: Re: Why would it make such a difference to move mysqld to anothermachine? Message-ID: <EC1DA137-76D2-44AA-A7F2-75FE7A3DA05C@identry.com> In-Reply-To: <48721BB5.1050203@infracaninophile.co.uk> References: <E46D5ADF-51F4-4393-BDEC-79FE02E4A574@identry.com><4870894E.7090708@infracaninophile.co.uk> <200807061759.12129.fbsd.questions@rachie.is-a-geek.net> <FF8482A96323694490C194BABEAC24A002F389EE@Email.cbord.com> <48721BB5.1050203@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes, that could be the case if the database was transferred by > doing mysqldump > on the first machine and then loading the dump on the second. This is indeed what I did. Odd that you ask this question, because my very first guess about this issue was that the database was corrupted in some way. However, I could not find any evidence of corruption, per se. I didn't realize that mysql records could become 'fragmented'... I guess this means the records are fragmented on disk as the database file is updated over time. The records in question (mainly product data) are not changed very often, and had been moved (using mysqldump) to this new machine in the last 6 weeks or so. So this doesn't sound like a likely cause. However, a very interesting thing to know... -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC1DA137-76D2-44AA-A7F2-75FE7A3DA05C>