On 2015-08-26 12:49:46 -0400, Tom Lane wrote: > As far as that goes, we do have fallback atomics code that's supposed to > work on anything (and not be unusably slow). So in principle, > resurrecting the Alpha spinlock code ought to be enough to get back to the > previous level of support. Coding Alpha atomic primitives would likely > be worth doing, if there's somebody out there who's excited enough to take > it on; but that could happen later, and incrementally.
Actually, on linux and most other OSs it should just use the generic gcc based implementation and be pretty close to optimal. The only thing it'd need would be to define the memory barriers, so the fallback implementation of those isn't used. But I really strongly object to re-introducing alpha support. Having to care about data dependency barriers is a huge pita, and it complicates code for everyone. And we'd have to investigate a lot of code to actually make it work reliably. For what benefit? > > A buildfarm machine would be mandatory, too. > > That, however, is not negotiable. If we really were to re-introduce this we'd need an actual developer machine to run tests against. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
