WordPress.org

1. phillprice
   Member
   Posted 2 years ago #

   Hey - recently I've seen these popping up all over the place. I'm using 3.1.3 version on WP 2.9.2

   WordPress database error The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay for query insert into wp_yarpp_related_cache (reference_ID,ID,score) SELECT 999, ID, (0+ (MATCH (post_title) AGAINST ('river ')) * 1+ COUNT( DISTINCT tagtax.term_taxonomy_id ) * 1) as score
   from wp_posts
   left JOIN wp_term_relationships AS thistag ON (thistag.object_id = 999 )
   \t\tleft JOIN wp_term_relationships AS tagrel on (tagrel.term_taxonomy_id = thistag.term_taxonomy_id
   \t\tAND tagrel.object_id = wp_posts.ID)
   \t\tleft JOIN wp_term_taxonomy AS tagtax ON ( tagrel.term_taxonomy_id = tagtax.term_taxonomy_id
   \t\tAND tagtax.taxonomy = 'post_tag')
   where (post_status IN ( 'publish', 'static' ) and ID != '999') and post_password =''
   group by id
   having score >= 2.50 and COUNT( DISTINCT tagtax.term_taxonomy_id ) >= 2 order by score desc limit 6 on duplicate key update date = now() made by require, require_once, include, related_posts, yarpp_related, yarpp_cache_enforce

2. mitcho (Michael Yoshitaka Erlewine)
   Member
   Posted 2 years ago #

   Hmm, interesting. I've never seen this particular error before, but you must just have a lot of posts. :) Turning off "considering" tags and/or categories might help, but I'll also see about adding that SET SQL_BIG_SELECTS=1 statement. Thanks Phill.

3. mitcho (Michael Yoshitaka Erlewine)
   Member
   Posted 2 years ago #

   @phillprice, are you still seeng this?

Topic Closed

This topic has been closed to new replies.