On 18/08/2016 11: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. > > But at the same time, applications should work, not just killed.
Therefore, I suggest something that makes the feature more useful and is not more difficult to implement. Timeouts split in alert-timeout and kill-timeout. You can define none, both or one of them. The kill-timeout is what you described. The alert-timeout just logs. You can define both, of course, the alert interval must be bellow the kill interval. With an alert-timeout DBA can understand how the applications and databases works and in future set an educated value for the kill-timeout. Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
