← Back to team overview

drizzle-merge team mailing list archive

Re: reclaiming mutex

 

This tree could / should also go in (has a lot of optimizer crash fixes) - I
had to re-fix some test cases that needed cleanup.
lp:~patrick-crews/drizzle/bug608416_test_updates


On Tue, Aug 17, 2010 at 9:53 AM, Patrick Crews <gleebix@xxxxxxxxx> wrote:

> So...
> Are / will the trees be in a good state before long (tarball day)?
>
> When I checked this morning, build had changes that needed to move to
> staging (and drizzle-build-debian-packaging was failing due to conflicts -
> new files and whatnot).  I was a little leery of touching the trees without
> asking somebody : )
>
> The only thing I'd really like to see merged in are the translation
> updates, but we do have a number of other patches sitting approved that we
> could merge as well.
>
> Thanks,
> Patrick
>
>
> On Mon, Aug 16, 2010 at 12:48 PM, Monty Taylor <mordred@xxxxxxxxxxxx>wrote:
>
>> Aha!
>>
>> I believe I have found the problem... vijay missed setting the default
>> value on one of the innodb params. Unfortuntely (or fortuntely, so that
>> the error was obvious enough to catch) ... the variable was
>> buffer_pool_size :)
>>
>> I'm gonna push a fix to build in just a sec and see if it fixes it. So I
>> reclaim the mutex - gimme a few more hours...
>>
>> Monty
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~drizzle-merge
>> Post to     : drizzle-merge@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~drizzle-merge
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>

Follow ups

References