Subject | Re: [IB-Architect] Synchronisation between classic architecture server processes |
---|---|
Author | Ann Harrison |
Post date | 2000-03-23T15:02:34Z |
At 12:50 PM 3/23/00 +1100, Jan Mikkelsen wrote:
as a separate process, depending on the platform. It handles short term
page locks and a variety of other locks - like the shared lock that each
transaction gets on tables it reads, locks transactions take out on their
own transaction id, etc.
exclusively through the lock manager and the database ... and
events, but that's a separate issue.
Ann
>How is synchronisation performed between classic architecture serverYes. There is a lock manager, variously implemented in shared memory or
>processes?
>
>I assume that there are short locks on pages in the database file. Ie:
>acquire write lock, read/modify page, write page, release lock, or acquire
>read lock, read page, release lock.
>If this locking exists, how is it implemented? If not, how is page level
>synchronisation performed? Does the implementation vary significantly by
>platform?
as a separate process, depending on the platform. It handles short term
page locks and a variety of other locks - like the shared lock that each
transaction gets on tables it reads, locks transactions take out on their
own transaction id, etc.
>I assume higher level isolation is totally taken care of by the protocolsRight. Under the classic architecture, the processes communicate
>around the on disk structure with transaction numbers, and so needs no
>separate IPC channel.
exclusively through the lock manager and the database ... and
events, but that's a separate issue.
Ann