From: Date: July 3 2008 11:27pm
Subject: RE: bzr commit into mysql-6.0-falcon branch (lars-erik.bjork:2723) Bug#36991
List-Archive: http://lists.mysql.com/commits/48990
Message-Id: <001e01c8dd53$8a8e8840$9fab98c0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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.