Markus Schiltknecht <markus@bluegap.ch> writes:
> what are the assumptions PostgreSQL normally does about atomic
> operations?
Rule of thumb: you want to touch shared memory, you use a lock.
There are a few places that violate it, but in general you'd better have
a pretty darn good reason to not use a lock.
Offhand I recall that we assume TransactionId can be stored atomically
in a couple of places where locking would be inconvenient. (This is one
of the good reasons for not wanting to widen TransactionId to 64 bits
... the assumption would then fail on some platforms.) I do not believe
we assume that pointers can be stored atomically.
regards, tom lane
