On Tue, Feb 26, 2008 at 3:42 AM, Merten, Alexander (External)
<Alexander.Merten.External_at_eads.com> wrote:
>
>
>
> Dear all,
>
> can anyone help me on this: How does Subversion handle commits, that
> practically happen at the same time?
> Are commits handled sequentially, like e.g.
>
> Start-Commit c1
> Pre-Commit c1
> Post-Commit c1
> Start-Commit c2
> Pre-Commit c2
> Post-Commit c2
>
>
> Or is there a parallization between commits, e.g.
>
> Start-Commit c1
> Start-Commit c2
> Pre-Commit c1
> Pre-Commit c2
> Post-Commit c1
> Post-Commit c2
>
> If the second applies, is there any restriction on how those commits can
> interleave? E.g. is the following technically possible
>
> Start-Commit c1
> Pre-Commit c1
> Start-Commit c2
> Pre-Commit c2
> Post-Commit c2
> Post-Commit c1
I believe commits are serial, first-come first-served. Whomever's
commit transaction gets started first by the server will execute
first, everyone else will wait in line. Otherwise, the atomic nature
of commits wouldn't be possible.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-26 16:23:08 CET