From owner-freebsd-database@FreeBSD.ORG Wed Oct 12 22:23:37 2005 Return-Path: X-Original-To: freebsd-database@freebsd.org Delivered-To: freebsd-database@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 453E916A41F for ; Wed, 12 Oct 2005 22:23:37 +0000 (GMT) (envelope-from justin.bastedo@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DC843D4C for ; Wed, 12 Oct 2005 22:23:35 +0000 (GMT) (envelope-from justin.bastedo@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so143784wxc for ; Wed, 12 Oct 2005 15:23:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=muzSjbSsjVVSu1wmrXXdHO3JOMpS54+Yg7lbpRsBkox7VZ6U0U8EVFrmJHi25q4yzAX3Csoxqlh44Gi3ViEXLOVoQlmi5f+xeMfOyRT7PHPsgrgAVhMwmeuAfSpO3cYTqRPR80wegxtCloZDJl2lvMDSRY+VgLk9+h7NokJH318= Received: by 10.70.131.10 with SMTP id e10mr354119wxd; Wed, 12 Oct 2005 15:23:35 -0700 (PDT) Received: by 10.70.35.7 with HTTP; Wed, 12 Oct 2005 15:23:35 -0700 (PDT) Message-ID: <8a5255240510121523p39c76508n99451832bbb9fdc9@mail.gmail.com> Date: Wed, 12 Oct 2005 15:23:35 -0700 From: Justin Bastedo To: NMH In-Reply-To: <20051012221241.24236.qmail@web32913.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8a5255240510121434k6c2c1028x646120b245343a0f@mail.gmail.com> <20051012221241.24236.qmail@web32913.mail.mud.yahoo.com> Cc: FreeBSD-DataBase , questions Subject: Re: Mysql server not able to stay running on anything but Linux? X-BeenThere: freebsd-database@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Database use and development under FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2005 22:23:37 -0000 Yeah i still have quite a way to go to catch up on you on actual usage, but would be good to see if the problem persisted on the 5.4-STABLE release. As Kris said "a number of bugs have been fixed in 5.4-RELEASE.." it might be a good test. Also does this persist across all the versions of mysql? I know they just launched the RC of 5.0, may be able to leverage that a bit i know they are really pushing to get that released, and might be nice knowing that this problem is fixed in the new release. I'm definately interested to see what the final solution is on this matter. I can easily forsee our db load getting close to that level within the next couple of months depending on how these contracts play out. Justin