18.08.2016 10:37, liviuslivius wrote: > > > W dniu 2016-08-18 09:26:22 użytkownik Vlad Khorsun <hv...@optima.com.ua> > napisał: >> 18.08.2016 10:08, liviuslivius пишет: >>> Hi Vlad, >>> >>>>> I.e interactive Delphi application that fetch only really shown records >>>>> will get error >>>>> when user press "Down" key, >>>> >>>> If user fetch one record per hour - yes, such application should be >>>> better rewritten >>> >>> Is this query in different state that can be distinguished from "running" >>> queries? I see that yes. >>> And should be possibility to exclude it from this feature or make 2 >>> different settings for that. >> >> Could you show good reasons to do it ? Real use case also welcome. ... > Query timeout is good for queries that consume CPU resources and not finished > in limited time.
CPU is important but not the only resource. > But queries that feth e.g. 100 records for user and wait to fetch rest do not > consume much resources > and user can fetch (rest or next portion) e.g. after 10 minutes. It is too generic. Query could use 1GB for sorting and fetch very slow > And that queries are not problem for DBA. Yes, such queries consume some > resources but not extensivly. See above, it is not as easy. Also, such queries not allows to commit corresponding transaction and it could lead to blocked garbage collection, growing active part of TIP and force other attachments to consume more resources. > But feature like timeout is for queries that can utilize all server resources. Regards, Vlad ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
