bzr commit into mysql-5.1-bugteam branch (satya.bn:2922) Bug#10206

[Satya B]

#At file:///home/satya/WORK/10206/mysql-5.1-bugteam-10206-push/ based on revid:satya.bn@stripped

 2922 Satya B	2009-06-02
      Followup Fix for BUG#10206 - InnoDB: Transaction requiring Max_BinLog_Cache_size > 4GB 
                                   always rollsback.
      
      There is failure on pushbuild machines which are using old compilers complaining about
      ULLONG_MAX declaration. Changing this to ULONGLONG_MAX to solve the problem.
      modified:
        sql/mysqld.cc

per-file messages:
  sql/mysqld.cc
    Change ULLONG_MAX to ULONGLONG_MAX for the max_binlog_cache_size option
=== modified file 'sql/mysqld.cc'
--- a/sql/mysqld.cc	2009-06-02 08:14:41 +0000
+++ b/sql/mysqld.cc	2009-06-02 12:37:47 +0000
@@ -6583,7 +6583,7 @@ log and this option does nothing anymore
   {"max_binlog_cache_size", OPT_MAX_BINLOG_CACHE_SIZE,
    "Can be used to restrict the total size used to cache a multi-transaction query.",
    (uchar**) &max_binlog_cache_size, (uchar**) &max_binlog_cache_size, 0,
-   GET_ULL, REQUIRED_ARG, ULONG_MAX, IO_SIZE, ULLONG_MAX, 0, IO_SIZE, 0},
+   GET_ULL, REQUIRED_ARG, ULONG_MAX, IO_SIZE, ULONGLONG_MAX, 0, IO_SIZE, 0},
   {"max_binlog_size", OPT_MAX_BINLOG_SIZE,
    "Binary log will be rotated automatically when the size exceeds this \
 value. Will also apply to relay logs if max_relay_log_size is 0. \