Firebird 2 Bug Fixes

Firebird 2 Bug Fixes
(CORE-3091) The built-in function POWER(X, Y) would not work when the X argument was negative
and the Y value was a scaled numeric with scale 0.
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-3079) A transaction that involved events would slow down inserts in the same transaction markedly.
fixed by V. Khorsun
~ ~ ~
(CORE-3067) Objects were not being unmapped when shared memory was closed.
fixed by A. Peshkov
~ ~ ~
(CORE-3064) Using both the procedure name and an alias for it inside an explicit plan would crash
the server.
fixed by D. Yemanov
~ ~ ~
(CORE-3041) The engine could hang when working with a read-only database.
fixed by V. Khorsun
~ ~ ~
(CORE-3034) An unhandled exception condition could throw “Bugcheck 300 (can't find shared latch)”.
fixed by V. Khorsun
~ ~ ~
(CORE-3016) On disconnect, the engine could erroneously report “Fatal lock manager error: invalid lock
id (0), errno: 0” in firebird.log.
fixed by V. Khorsun
~ ~ ~
(CORE-3015) Various occurrences of “Cannot initialize the shared memory region” errors were being
reported.
fixed by V. Khorsun
~ ~ ~
(CORE-2999) The message “SCH_validate -- not entered” was being logged in firebird.log when a Classic
server connection that had used events was finished.
fixed by V. Khorsun
12