Re: Making fsfs generate unique transaction names

On 6/19/07, Blair Zajac <blair@orcaware.com> wrote:
> The only thing is, I'd like to have a separate lock for updating the transaction
> current count then using the current filesystem lock. There's no reason to lock
> the filesystem for a commit while incrementing the transaction counter.
>
> So I'm thinking of having two new files:
>
> 1) transaction-current: holds the base-36 number
> 2) transaction-current-lock: holds the lock for incrementing transaction-current.
>
> Or maybe transaction-count and transaction-count-lock, or exen txn-count,
> txn-count-lock.
>
> Comments?

Isn't adding yet another file and yet another lockfile getting a tad
overkill? -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 19 20:39:39 2007