19.02.2017 5:21, Leyne, Sean wrote:
>
>
>>> If I read the documentation correctly, a statement which performed
>>> (say) a SELECT against a table that
>> > follows a NATURAL scan, which is 'paused' awaiting the next Fetch, would
>> run into the timeout, even > though there is no "cost" to the
On 08/18/2016 06:26 PM, Vlad Khorsun wrote:
> 18.08.2016 18:08, Dimitry Sibiryakov wrote:
>> 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
18.08.2016 18:08, Dimitry Sibiryakov wrote:
> 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
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
17.08.2016 22:07, Dimitry Sibiryakov wrote:
> 17.08.2016 20:44, Vlad Khorsun wrote:
>>- can't be greater than (non-zero) value at config
>
>I.e there is no way for DBA to make exceptions for some queries that are
> known to be
> good, but long, right?
Right. Smart DBA should set
