Some parts of the server was compiled with BIG_TABLES define set,
other parts without... Or at least, when include/my_base.h was read,
the setting of BIG_TABLES was different. So on some files, it is a
32bit quantity, others it is a 64bit quantity... I am surprised it
hasn't lead to a crash because there are some pointers stored in
struct system_variables.
If you're using ccache, clear the cache before building from clean
again by executing "ccache -C"
Regards,
Antony
On 15 Oct 2008, at 18:16, Erik Ljungstrom wrote:
> Even though that particular warning seem pertinent to the microslow
> patch it may stem from this upstream bug
> http://bugs.mysql.com/bug.php?id=35346 ?
>
> --
> Variables out of bounds on 32bit
> https://bugs.launchpad.net/bugs/284123
> You received this bug notification because you are a member of
> OurDelta-
> developers, which is the registrant for OurDelta.
>
> Status in OurDelta - Builds for MySQL: New
>
> Bug description:
> When installing on 32bit Ubuntu Hardy and Debian Etch, the server
> issues a warning about variables that appear to default to 64bit
> integer values. These warnings are not displayed on 64bit hardy and
> etch.
>
> Setting up mysql-server-5.0 (5.0.67-d6ourdelta15) ...
> Stopping MySQL database server: mysqld.
> 081016 17:47:00 [Warning] option 'log_slow_rate_limit': unsigned
> value 18446744073709551615 adjusted to 4294967295
> 081016 17:47:00 [Warning] option 'min_examined_row_limit': unsigned
> value 18446744073709551615 adjusted to 4294967295
> Starting MySQL database server: mysqld.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ourdelta-developers
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~ourdelta-developers
> More help : https://help.launchpad.net/ListHelp
Hi,
I have seen bugs like this before.
My 5 minute guess as to the nature of this bug:
Some parts of the server was compiled with BIG_TABLES define set,
other parts without... Or at least, when include/my_base.h was read,
the setting of BIG_TABLES was different. So on some files, it is a
32bit quantity, others it is a 64bit quantity... I am surprised it
hasn't lead to a crash because there are some pointers stored in
struct system_variables.
If you're using ccache, clear the cache before building from clean
again by executing "ccache -C"
Regards,
Antony
On 15 Oct 2008, at 18:16, Erik Ljungstrom wrote:
> Even though that particular warning seem pertinent to the microslow bugs.mysql. com/bug. php?id= 35346 ? /bugs.launchpad .net/bugs/ 284123 d6ourdelta15) ... rate_limit' : unsigned 51615 adjusted to 4294967295 row_limit' : unsigned 51615 adjusted to 4294967295 _______ _______ _______ _______ _______ _____ /launchpad. net/~ourdelta- developers /launchpad. net/~ourdelta- developers /help.launchpad .net/ListHelp
> patch it may stem from this upstream bug
> http://
>
> --
> Variables out of bounds on 32bit
> https:/
> You received this bug notification because you are a member of
> OurDelta-
> developers, which is the registrant for OurDelta.
>
> Status in OurDelta - Builds for MySQL: New
>
> Bug description:
> When installing on 32bit Ubuntu Hardy and Debian Etch, the server
> issues a warning about variables that appear to default to 64bit
> integer values. These warnings are not displayed on 64bit hardy and
> etch.
>
> Setting up mysql-server-5.0 (5.0.67-
> Stopping MySQL database server: mysqld.
> 081016 17:47:00 [Warning] option 'log_slow_
> value 184467440737095
> 081016 17:47:00 [Warning] option 'min_examined_
> value 184467440737095
> Starting MySQL database server: mysqld.
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/