YANG Xudong <yangxud...@ymatrix.cn> writes: > This patch set tries to add loongarch64 native spin lock to postgresql.
This came up before, and our response was https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1c72d82c2 In principle, at least, there is no longer any need for machine-specific s_lock.h additions. Is there a strong reason why the __sync_lock_test_and_set solution isn't good enough? regards, tom lane
