18.08.2016 16:55, Vlad Khorsun wrote: > Global timeout is a last line of defense for DBA against bad apps, wrong > queries, > developer mistakes, unlucky days (dropped some indices last week but now some > queries > got crazy) and so on. It is *last* line, therefore it should be used with > maximum care.
What can be an advantage of this feature over cron-ed script chat check monitoring tables and send DBA mail with list of bad queries? > For example: as developer you may like to set session level timeout in > your dev tool > to avoid need to kill manually query you writting and forget to specify join > condition > for 25th and 26th tables in it. As a developer I would not ever run such query on production database. Besides, I have no idea how to choose the value of timeout. And yes, I would hardly be a user of this marketing feature. -- WBR, SD. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
