From owner-freebsd-questions@FreeBSD.ORG Thu May 1 19:52:09 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25C521065678 for ; Thu, 1 May 2008 19:52:09 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id E49CF8FC17 for ; Thu, 1 May 2008 19:52:08 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id BB6F01CC91; Thu, 1 May 2008 11:52:07 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Thu, 1 May 2008 21:52:05 +0200 User-Agent: KMail/1.9.7 References: <200805011913.DSZ93243@jmu.edu> In-Reply-To: <200805011913.DSZ93243@jmu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805012152.06354.fbsd.questions@rachie.is-a-geek.net> Cc: John Subject: Re: Recovering mysql data - mysqlbinlog X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2008 19:52:09 -0000 On Thursday 01 May 2008 21:13:41 John wrote: > Thank you Mel and Paul for the suggestions. From what I understand the > general query log is more for debugging and the binary log is for point in > time recovery and replication. I'll be adding a my.cnf file (using the > my-large.cnf as a skeleton) soon. I'm glad the issue was caught earlier on > and now I'm the wiser thanks to you guys. I wonder why the default is no. > I can't think of anyone who wouldn't find the binary logging beneficial. I can think of a reason for FreeBSD. The binary logs are never deleted and upon every server restart a new one is created. If you're like me, developing on a laptop with a webenvironment including 'Mysql server', shutting down your laptop daily, you quickly find yourself having full /var partition. People running dedicated or semi-dedicated MySQL installations, are encouraged to tweak their installation anyway. The most common ones being: - put the binary logs on a large enough disk, if possible a seperate disk all together for performance. - by default, /tmp is used for temporary sorting tables, when JOINs demand it. If that's a small partition or worse a 64MB memory disk, expect to get in trouble, system wide. Use the tmpdir configuration variable. - thread_concurrency as indicated in the templates - skip-networking for security if all traffic is local - sort and key buffer + max_connections to limit/max out memory usage. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.