Hi, My DEV server is used by many people creating apps throughout the company. Consequently, I have no insight in the efficiency or quality of their SQL. This is an accepted state of affairs.
However, 'developers' have repeatedly managed to crash mysqld because their queries are huge, don't use indexes, etc. At those times, the load on the box (dual-CPU, 4GB RAM) is 23, and I can't even ssh into it anymore. Is there a way to kill queries automatically if they take longer than x seconds to complete? I'm not sure (form the documentation) if this is where 'interactive_timeout' can be used. Lowering max_join_size could be an option too (it's currently 100,000,000), but I don't want to break people's existing apps that may rely on this hight join size. Thanks, -- Martijn van den Burg ASML ITM&S MySQL/TIBCO Support -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
