27.10.2013 Views

Firebird 2 Bug Fixes

Firebird 2 Bug Fixes

Firebird 2 Bug Fixes

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

fixed by D. Yemanov<br />

~ ~ ~<br />

<strong>Firebird</strong> 2 <strong>Bug</strong> <strong>Fixes</strong><br />

(CORE-3524) The server would crash while compiling a stored procedure that was in use.<br />

fixed by V. Khorsun<br />

~ ~ ~<br />

(CORE-3517) The built-in function LPAD() would crash the server with a string passed as the second<br />

parameter.<br />

fixed by A. dos Santos Fernandes<br />

~ ~ ~<br />

(CORE-3440) The server would crash if isc_que_events() had no events queued.<br />

fixed by V. Khorsun<br />

~ ~ ~<br />

(CORE-3374) The server could crash or corrupt data if SELECT WITH LOCK was issued against records<br />

not in the latest format.<br />

fixed by D. Yemanov<br />

~ ~ ~<br />

(CORE-3320) Some forms of the MERGE syntax could cause the server to crash.<br />

fixed by A. dos Santos Fernandes<br />

~ ~ ~<br />

Database Monitoring<br />

(CORE-3625) MON$IO_STATS was not reporting page writes performed asynchronously (at the AST<br />

level).<br />

fixed by D. Yemanov<br />

~ ~ ~<br />

(CORE-3138) An internal error or a crash would occur when accessing any MON$ table after altering<br />

its structure.<br />

fixed by D. Yemanov<br />

~ ~ ~<br />

(CORE-2286) Selecting from MON$CALL_STACK from within a PSQL module could return no rows<br />

in some cases.<br />

8

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!