Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Firebird</strong> 2 <strong>Bug</strong> <strong>Fixes</strong><br />
(CORE-3001) The POSIX installation routine was failing to create the “firebird” user and group.<br />
fixed by A. Peshkov<br />
~ ~ ~<br />
(CORE-2919) The POSIX installation script was ignoring non-standard ports.<br />
fixed by A. Peshkov<br />
~ ~ ~<br />
(CORE-2865) A segmentation fault would occur when the Superserver binary on POSIX was restarted.<br />
fixed by A. Peshkov<br />
~ ~ ~<br />
(CORE-2845) The build process on Solaris would stop with the message: “need to use SFIO”. On the<br />
whole, Solaris 10 no longer requires SFIO - the 64-bit builds do not suffer the issue with the maximum 255 file<br />
descriptors and there are simple work-arounds for 32-bit builds. See this article for details.<br />
However, the issue still affects Solaris 10 3/05 through Solaris 10 11/06. Some patches are needed to correct<br />
the problem.<br />
For the time being, the easiest solution is to leave the define in the code, but comment it with the relevant<br />
information for Solaris 10. The define can be removed if the patches have been applied or the user is running<br />
an unaffected version of Solaris 10.<br />
Updated information concerning this issue has been inserted into common.h. Anyone building 32-bit <strong>Firebird</strong><br />
on Solaris 10 will have to make an informed decision according to the version and build/patch level of Solaris<br />
before uncommenting the SFIO define.<br />
fixed by P. Beach<br />
~ ~ ~<br />
(CORE-2814) On SPARC, the server was crashing in the routine map_sort_data with a bus error.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-2572) Locks of type LCK_page_space were being processed incorrectly on big-endian machines.<br />
fixed by A. Peshkov<br />
~ ~ ~<br />
Command-line Utilities<br />
gbak<br />
(CORE-3003) The “suspend check” on a stored procedure could cause a gbak restore to fail.<br />
20