[MDEV-5752] mysqldump fails with The SELECT would examine more than MAX_JOIN_SIZE rows Created: 2014-02-27 Updated: 2014-03-02 Due: 2014-03-27 Resolved: 2014-03-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.33a |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | tem (Inactive) | Assignee: | Elena Stepanova |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
FreeBSD 9.1-RELEASE-p4 |
||
| Description |
|
sometimes it fails, not each time:
+ the problem, that sql_big_selects=OFF by default. on mysql start:
my.cnf:
|
| Comments |
| Comment by Sergei Golubchik [ 2014-02-27 ] | |
|
In fact, max_join_size is 18446744073709551615 by default, and sql_big_selects is ON. Do you use our binaries or from the FreeBSD Ports? Perhaps the defaults there are different (though, it's unlikely). Perhaps one of the applications has changed max_join_size on your server, like
| |
| Comment by tem (Inactive) [ 2014-02-27 ] | |
|
from /usr/ports/databases/mariadb55-server there is only one application on server, and it does not set max_join_size (rechecked all sripts), | |
| Comment by Elena Stepanova [ 2014-02-27 ] | |
|
Please also check if you have cnf files in other default locations, which the server might have picked up in addition to the desired one. They cannot set sql_big_selects, but might (and probably do) set max_join_size=16M, which, in turn, will cause automatic switch-off for sql_big_selects. Or, if it's easier, try to start server with the explicit --defaults-file pointing at the cnf that you pasted, and see whether the problem persists. | |
| Comment by tem (Inactive) [ 2014-02-28 ] | |
|
oops. | |
| Comment by tem (Inactive) [ 2014-03-02 ] | |
|
no more errors in mysqldump. |