Provide ability for engine to forcely make DISCONNECT for each client that
starts TX and keep it uncommitted more than some limit of time
-----------------------------------------------------------------------------------------------------------------------------------------
Key: CORE-4238
URL: http://tracker.firebirdsql.org/browse/CORE-4238
Project: Firebird Core
Issue Type: Improvement
Affects Versions: 3.0 Alpha 1
Reporter: Pavel Zotov
If TX has been opened in any mode tha is NOT { read_committed | read_only }
then its very easy to force database to accumulate in it huge amount of
versions of updated / deleted records: it's sufficient just avoid
commit/rollback such TX. This leads to "heavy work" for GC and almost always
decrease application performance (all DML except insertions).
It will be useful if DBA could assign (in database.conf or firebird.conf)
maximum allowed timeout for ANY transactions that have been started in NOT (
read_committed | read_only ) mode - even if they started by SYSDBA or db
owner. Such TXs should be forcelly committed (if no changes occured) or
rollbacked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
