"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> When reading Tom's comment about the bug in my "use latestCompletedXid
> to slightly speed up TransactionIdIsInProgress" patch, I remembered that
> I recently stumbled across GCC builtins for atomic test-and-test and
> read/write reordering barriers...
> Has anyone looked into those? It seems that those could be used to
> provide a fallback spinlock implementation - though maybe we already
> cover all interesting targets, and it's not worth the effort.
It doesn't seem very interesting given that (a) we already have working
code for this area, and (b) gcc is not our only target compiler.
regards, tom lane