A few words about the shared memory and files

Even if running in the Classic (isolated process) mode, Firebird needs some data to be available to all the running server processes. There are four kinds of information that must be shared:

  • Lock table. It’s the vital part of the lock manager and its primary goal is to synchronize access to various resources that can be read or modified simultaneously.
  • Event table. Every time a posted event is committed, the server needs to find all the subscribers and redirect the event delivery to processes handling the appropriate user connections.
  • Monitoring snapshot. It keeps the latest known state of all the running worker processes and it gets updated once some user connection attempts to access the monitoring tables in a new transaction.
  • Trace configuration. It contains the information required for the worker processes to react on the currently active tracing events and log the appropriate notifications.

Continue reading at Dmitry Yemanov’s blog.

Searching for Firebird programmer

I got this in my email box, maybe some of you would be interested:

Dear Carlos,
I came across your name asking developers to send details of large companies who use firebird databases. I am actually an end-user who has the open mind to want a firebird database but cannot find anyone who does this programming. I am based in the UK and am told to ‘steer away’ from firebird as it is not proven, etc. etc.
It really is quite disappointing and seems that there are many others like myself who would like to have an alternative but cannot find a developer. So I am the horse looking for water to drink – but there is no water…not like you describe leading the client to the water but not getting them to drink.
Any suggestions?
JT <tse.tse@ntlworld.com>
PS: It is weird that in the actual days, with so many great case studies published, there are still people who thinks FB is a “toy”.

Firebird roadmap has been updated

From Dmitry Yemanov:

The project roadmap has been updated a bit. The change is to boost the v2.1.5 and v2.5.2 releases at the cost of slightly delaying the v3.0 Alpha release.

Firebird 2.1.4 was released exactly one year ago, so now it’s a promised time for v2.1.5. It has 53 bugs fixed and no critical issues remaining unresolved. Firebird 2.5.1 was released more than 5 months ago and the expected release date for v2.5.2 is approaching the next month. It has 45 issues resolved up-to-date and a few more are in the pipeline. So it makes a lot of sense to release them sooner rather than later.

The v3.0 Alpha release will be going through the preparation stage while all three release candidates (v2.0.7, v2.1.5, v2.5.2) are being field tested, so it’s likely to appear shortly after the aforementioned releases, in the second quarter.

Thanks for your understanding.

1 22 23 24 25 26 100