Re: Making fsfs generate unique transaction names

[Blair Zajac]
> 3) use base-36 digits and some way of atomically incrementing it
> + sequential
> + short
> - need to write code to atomically increment the counter
> a) use sqlite to store the current value
> b) use yet another file that is atomically updated and write the code
> that
> does this

I was thinking 3b. Why not? Is there a concern about extra network
I/O round trips for SAN backends? A function to open, lock, read,
increment, write, unlock, close, return the new value, sounds like
about 15 lines of code, particularly if the function to increment a
base-36 number already exists in BDB.