18.08.2016 18:59, Dmitry Yemanov wrote: > Prevent production server from being unexpectedly overloaded *before* > DBA can analyse such cases and take actions to avoid them. Typical cases: > > - possibly heavy ad-hoc queries parallel to fast well-tuned ones > - unlucky database/application upgrade (e.g. some plans are screwed) > > i.e. if you don't want some guilty connection(s) to dramatically affect > the whole system.
May be there are simpler and safer solutions for these problems? How about to deny implicit Cartesian join?.. Or deny join of two natural streams, forcing them into hash or merge join? Btw, do merge outed joins already work? Can it prepare merged streams in parallel? Using hash-sort for that? In conjunction with upcoming tablespaces and manual placing them into independent drives, it can make Firebird lighting fast. How about versioned index nodes to prevent garbage collection from affecting performance of queries? Index-only scans could help as well. Vlad talked about implementing it two years ago, but obviously he gave up. -- WBR, SD. ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
