Geeklog Forums

After adding a 14th topic I got an sql error:
Wed Nov 19 12:11:14 2003 - 1104: The SELECT would examine more rows than MAX_JOIN_SIZE. Check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is ok. SQL in question: SELECT COUNT(*) AS count from gl_stories WHERE (tid IN ('constitution','foreign','General','gospodarkausa','historiausa','imigracja','kanada','lacina','lottery','metodologia','systemypolityczne','theatre','uspresidents','wpquiz'))

Tried to figure out how to solve however I got lost.
Any help appreciated.

---

Geeklog Polish Support Team

This sounds like you have a mySql (You are using mysql right?) error relating to the number of rows that are allowed to be involved in a single query. Interestingly, that query is only from a single table.

I can see 3 possible problems:

1. max_join_size is set to a small value (Are you using a hosting service that has intentionally limited query sizes?)

2. You have a LOT of articles, higher than the max_join_size

3. Something I don't know about.

Basicly, a db admin (or you, if you have the privlages,) need to set mysql to use a larger max_join_size. (Check google for tutorials on setting up mysql parameters)

I am surprised you would run into problems with the join size though on that particular table. It shouldn't be very large.

Was you site functioning before you added that 14th topic? or have you been still building your site?


Alex~
3.

Can you do a SHOW Variables from mysql and post the results?

Thanks

Thank you guys for responding to my issue.
Yes I'm using MySql.
1. I'm using www.host.sk services and there are sme limitations however don't know about the one you mentioned.
2. I have c.a. 70 articles (not much I guess) however there are some big ones. Could this be a reason?
Yes the site has been functioning smoothly and still it is, after I removed manually the 14th element from the db. The site is being constantly developed. amerykanistyka.host.sk

---

Geeklog Polish Support Team

Um. Silly question: How would I do this?

---

Geeklog Polish Support Team

Not silly for someone that is not use to using a db.

Use phpmyadmin and on from the sql tab, issue SHOW VARIABLES;

My hunch is it doesn't have to do with max_join_size. Unless yours is really low.

My gut says, it might take a while to figure this one out.

I can get geeklog to work just fin with a SQL_MAX_JOIN_SIZE = 30. I'm guessing that yours is much higher.

What version of mysql are you on?

Quite a long list. Can't much make out of it.
ver. 4.0.16-Max

Variable_name Value
back_log 50
basedir /
bdb_cache_size 8388600
bdb_log_buffer_size 262144
bdb_home /var/lib/mysql/
bdb_max_lock 10000
bdb_logdir
bdb_shared_data OFF
bdb_tmpdir /tmp/
bdb_version Sleepycat Software: Berkeley DB 3.2.9a: (October 1...
binlog_cache_size 32768
bulk_insert_buffer_size 8388608
character_set latin1
character_sets latin1 big5 czech euc_kr gb2312 gbk latin1_de sjis...
concurrent_insert ON
connect_timeout 5
convert_character_set
datadir /var/lib/mysql/
default_week_format 0
delay_key_write ON
delayed_insert_limit 100
delayed_insert_timeout 300
delayed_queue_size 1000
flush OFF
flush_time 0
ft_boolean_syntax + -> ft_min_word_len 4
ft_max_word_len 254
ft_max_word_len_for_sort 20
ft_stopword_file (built-in)
have_bdb YES
have_crypt YES
have_innodb YES
have_isam YES
have_raid YES
have_symlink YES
have_openssl NO
have_query_cache YES
init_file
innodb_additional_mem_pool_size 1048576
innodb_buffer_pool_size 8388608
innodb_data_file_path ibdata1:10M:autoextend
innodb_data_home_dir
innodb_file_io_threads 4
innodb_force_recovery 0
innodb_thread_concurrency 8
innodb_flush_log_at_trx_commit 1
innodb_fast_shutdown ON
innodb_flush_method
innodb_lock_wait_timeout 50
innodb_log_arch_dir ./
innodb_log_archive OFF
innodb_log_buffer_size 1048576
innodb_log_file_size 5242880
innodb_log_files_in_group 2
innodb_log_group_home_dir ./
innodb_mirrored_log_groups 1
innodb_max_dirty_pages_pct 90
interactive_timeout 90
join_buffer_size 131072
key_buffer_size 134217728
language /usr/share/mysql/english/
large_files_support ON
local_infile ON
locked_in_memory OFF
log OFF
log_update OFF
log_bin OFF
log_slave_updates OFF
log_slow_queries OFF
log_warnings OFF
long_query_time 10
low_priority_updates ON
lower_case_table_names OFF
max_allowed_packet 1047552
max_binlog_cache_size 4294967295
max_binlog_size 1073741824
max_connections 700
max_connect_errors 20000000
max_delayed_threads 20
max_heap_table_size 16777216
max_join_size 20000
max_relay_log_size 0
max_seeks_for_key 4294967295
max_sort_length 1024
max_user_connections 0
max_tmp_tables 32
max_write_lock_count 4294967295
myisam_max_extra_sort_file_size 268435456
myisam_max_sort_file_size 2147483647
myisam_repair_threads 1
myisam_recover_options OFF
myisam_sort_buffer_size 100663296
net_buffer_length 16384
net_read_timeout 30
net_retry_count 10
net_write_timeout 60
new OFF
open_files_limit 3510
pid_file /var/lib/mysql/db.host.sk.pid
Variable_name Value
log_error
port 3306
protocol_version 10
query_alloc_block_size 8192
query_cache_limit 1048576
query_cache_size 67108864
query_cache_type ON
query_prealloc_size 8192
range_alloc_block_size 2048
read_buffer_size 4190208
read_only OFF
read_rnd_buffer_size 262144
rpl_recovery_rank 0
server_id 0
slave_net_timeout 3600
skip_external_locking ON
skip_networking OFF
skip_show_database OFF
slow_launch_time 2
socket /var/lib/mysql/mysql.sock
sort_buffer_size 207618040
sql_mode 0
table_cache 512
table_type MYISAM
thread_cache_size 21
thread_stack 196608
tx_isolation REPEATABLE-READ
timezone CET
tmp_table_size 33554432
tmpdir /tmp/
transaction_alloc_block_size 8192
transaction_prealloc_size 4096
version 4.0.16-Max
wait_timeout 28800

---

Geeklog Polish Support Team

Well, definitely it has nothing to do with max_join_size....

Alex~

Did your host or yourself just upgrade the db to 4.0.16?


And yes I'm grabbing at straws here.

Everything is managed by the host. Incl. upgrades.

---

Geeklog Polish Support Team