18.08.2016 0:58, Adriano dos Santos Fernandes wrote: > Em 17/08/2016 15:44, Vlad Khorsun escreveu: > >> >> a) Statement execution timeout >> - timeout is set in milliseconds, there is no guarantee of exact precision >> (especially under high load). The only promise is that timeout will not >> happen earlier than specified > > Why milliseconds? If you're going to use seconds for session, seconds > here would be less confusing.
Initially i also thought about seconds. And, yes, i don't like to have different measures for similar things. But, technically, it is possible and it could be useful for testing purposes. Note, it have no sense for session idle timeout to be specified in ms. So i decided to discuss this point and it is good that you raise this question :) > Considering API calls, network times, etc, I doubt < 1s would be good > for anything here. What about 2500 ms ? :) I don't insist on milliseconds for statement timeouts. I want to hear more opinions. Btw, PG uses milliseconds :) >> - if timeout happens at moment with no client activity (for example between >> two >> fetch() calls) it will not take immediate effect, i.e. cursor remains >> open and >> resources is not freed > > What do you mean with "will not take immediate effect"? > > If it waits for the next fetch, it will not be effective for its purpose > - track bad written applications. Probably you right. I just described how statement cancellation works currently. Regards, Vlad ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
