Subject Re: [Firebird-Architect] Re: Vulcan architecture and lock tables
Author Vlad Horsun
> Slightly off-topic, but could I get back to per provider and per
> database lock tables whilst we are on the topic of lock tables?
>
> I remember this was discussed at the end of a SAS session during the
> 2005 Prague conference. My recollection of that discussion was that
> Jim and Ann both thought that per database lock tables were a good
> idea that had been considered in the past.
>
> Again in my recollection, Ann said that the reason for not doing per
> database lock tables in the 80's was the limited supply of semaphores
> on old Unices (16, or even 14, system-wide; these days 4096 is more
> normal).
>
> Looking forward to hearing opinions about the benefit and feasibility
> of per database lock tables.

As for me this is the very good to have feature especially for hosting
providers. When we host tens databases within one server lock table
contention can be much visible.

May be we can configure lock tables usage as we do with security
database ?

Regards,
Vlad