By andre75 on
I am recently getting a bunch of those:
mysql_query(): Unable to save result set in /pathtomysite/includes/database.mysql.inc on line 49.
Anyone knows what is happening?
This is how line 49 looks like:
$result = mysql_query($query, $active_db);
I would appreciate some tips about what is going wrong and how I can avoid this error.
Andre
Comments
bump
anyone?
Memory limit?
Allright. This is more than annoying. I fixed it by turning off a couple of blocks that would show up when I am browsing taxonomy_menu items. This fixed the problem.
The issue seems to be a memory limitation of my host.
What are the best practices to limit memory and queries.
I am using a bunch of modules to improve overall behavior (like pathauto) that obviously increase the number of queries.
However, I would like to streamline my drupal installation (e.g. have the cache in a file outside the database, have the session table outside the database).
Anyone familiar with these things?
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
Asking your hoster to
Asking your hoster to increase this limit (which one is it, btw?) or changing hosters sounds like easier to do than any of the modifiations you want to do.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
Maybe
That is true. But I should not have those kind of problems, since this also means that my site won't hold up to heavy loads.
I would much rather have less queries performed.
I ended up reducing the number of teasers shown per page.
This way the queries are less.
I am with Powweb, since they offer more Bandwidth than anyone else for only $7.77/mo (5GB/day).
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
Depends, if you use caching,
Depends, if you use caching, then an anonymous user will only generate 3 queries per page view.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
I am
I am caching but I have the feeling that many more requests are being generated (possibly by the blocks?). Otherwise the each side should be built faster.
It seems to be happening only when browsing through the navigation menu (Activities). Reducing the number of teaser defenitely solved this, despite caching.
Is there a way to monitor the number of queries?
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
The blocks are cached too,
The blocks are cached too, so they do not generate queries.
For looking at the generated queries, I recommend devel.module.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
I've googled a bit (did
I've googled a bit (did you?) and found several references to possibly broken tables. Try to repair them and see if the problem persists.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
Thanks
Thanks for the info. That is what I did first. In fact I even read somewhere that you have to do it multiple times to be effective. I did that too.
The only thing that worked so far is to limit the number of teasers that is being displayed. Ever since I set the number from 10 to 8 I havent gotten the error again.
I followed this procedure:
http://tinyurl.com/dklxf
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
Which version of Drupal are
Which version of Drupal are you running? Everything before 4.7 has a but where the revisions of a node get loaded for each node view. This can be a lot of data if you have a lot of revisions and might cause your problem.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
4.6.3
Let me see if I got this right:
Everything before 4.7 generates much more traffic besides the cache being turned on? That would be real bummer.
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com
No this has nothing to do
No this has nothing to do with traffic, but with the amount of memory Drupal uses on the mysql and php level. The amount of memory should go down for 4.7. This only applies if you are using revisions, though.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
No revisions
Thanks. Now I get it. I am not using revisions though. All changes are final. Interesting note though. I don't think it has anything to do with php memory, since I increased the limit in php.ini. I guess it is some mysql limit.
Anyways, one reason to upgrade.
I won't do it, until all modules are available for 4.7 and the distribuition itself has been out and tested for a while.
Andre
-------------------------------------------------
http://www.opentravelinfo.com
http://www.aguntherphotography.com