News for hackers. Stuff that matters.
Re:“POSIX advisory locks are broken by design” by emmelaich on Tuesday July 24, 2018 @09:18PM (#17606255)
If you want locks from the same user you'd use other mechanisms that file locks. File locks are for processes that don't have a lighter weight way to cooperate. (e.g. semaphores.)

Also, there's a reason that databases have processes dedicated to writing (e.g. Postgres writer process, Oracle dbwr)

Fun fact - IBM's MVS didn't have file locks.

Re:“POSIX advisory locks are broken by design” by pvg on Tuesday July 24, 2018 @09:33PM (#17606310)
there's a reason that databases have processes dedicated to writing

That's going to be a little tricky in an embedded db.

Re:“POSIX advisory locks are broken by design” by emmelaich on Tuesday July 24, 2018 @10:34PM (#17606543)
Sure, but you could still make sure writes are done in a mutex?
Re:“POSIX advisory locks are broken by design” by int_19h on Wednesday July 25, 2018 @03:12AM (#17607416)
Don't forget that it still needs to synchronize across process boundaries, too - two processes, both running SQLite, and both accessing the same database file, is a supported scenario.