24.06.2014 01:33, Nikolay Samofatov wrote: > > If this is what people want, it is possible to add new TPB parameter - > isc_tpb_inconsistency, and > permit it for READ_ONLY + READ COMMITTED transactions only. For as long you > don't use returned data > for anything important it is somewhat safe. > > With this change, I shall probably set up snapshots for NO_REC_VERSION mode > as well. This will make > this mode completely useless, but it will be safe at least. > > Dmitry, agreed?
I suppose a wider testing is necessary. And the current solution with config option is quite OK for that purpose. If the performance impact is really hardly noticable, then I have no problems with the "insensitive" mode becoming the default one. In this case, I'm not even sure a new transaction option is required (*) But if a noticable slowdown is found in some test cases, then I strongly believe the current "sensitive" behavior should remain the default one and the new "insensitive" mode should become optional via TPB. That said, I'm waiting for further Vlad's review before proceeding with committing and testing. (*) AFAIU, there's no other practical benefit in the "sensitive" mode except the performance. So if the "insensitivity" cost is nearly zero, then why bother supporting both? But so far, I'm a bit sceptical regarding the performance. Dmitry ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
