On 15-2-2019 17:59, Karol Bieniaszewski liviusliv...@poczta.onet.pl
[firebird-support] wrote:
> >>set FIREBIRD_LOCK env variable at *_system_* level and reboot.
>
> >>Be careful as wrong usage could damage database.
>
> Thank you Vlad. Can you explain more about risk?
As I understand it, the problem can surface if you use
Classic/SuperClassic and also an application using Firebird Embedded run
in a session with a different value for FIREBIRD_LOCK. In a situation
where both the server and the application access the same database, they
will not share the same lock files. This can lead to data corruption
because - for example - both can obtain a lock to modify the same page
given they use different lockfiles.
Mark
--
Mark Rotteveel
