List:Commits« Previous MessageNext Message »
From:Vladislav Vaintroub Date:July 3 2008 9:27pm
Subject:RE: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723) Bug#36991
View as plain text  
ok to push.
I'm wondering it would makes sense  rather delete
Configuration::maxTransactions as well and just use the
MAX_TRANSACTION_BACKLOG constant on a single place it is needed.
OTOH, if somebody decides that this value should be configurable again, your
current solution is probably most adequate.

> -----Original Message-----
> From: lars-erik.bjork@stripped [mailto:lars-erik.bjork@stripped]
> Sent: Thursday, July 03, 2008 1:24 PM
> To: commits@stripped
> Subject: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723)
> Bug#36991
> 
> #At bzr+ssh://bk-internal.mysql.com/bzrroot/server/mysql-6.0-falcon/
> 
>  2723 lars-erik.bjork@stripped	2008-07-03
>       bug#36991 falcon_max_transaction_backlog has no effect
> 
>       I have changed the maxTransactionBacklog to 1000 and have made
> the value
>       unconfigurable.


Thread
bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723) Bug#36991lars-erik.bjork3 Jul
  • RE: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723) Bug#36991Kevin Lewis3 Jul
    • RE: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723)Bug#36991Lars-Erik Bjørk4 Jul
  • RE: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723) Bug#36991Vladislav Vaintroub3 Jul