> > Everyone make mistakes and can, for example, miss one of
> > the join criteria producing cross join instead of inner join
> > and endless execution as result. Only thing we can do is
> > shutdown database for now.
> >
>
> But such problems will be caught in the design phase and/or function test
> phase, won't it? I see little use of a forced timeout when an
> application/database is put into production.

Don't forget - we deal with database. Database at design time and
database in production is a two (very) different things. Not all problems
can be seen at development time. But even if timeout useless in
production - why can't we do it for developers ?

> A way to manually cancel a query would be useful though.

Of course

Regards,
Vlad