On 2014-02-15 04:20:17 +0100, Florian Pflug wrote: > Another idea would be to do as you suggest and only mark the PGPROC pointers > volatile, but to additionally add a check for queue corruption somewhere. We > should > be able to detect that - if we ever hit this issue, LWLockRelease should find > a > PGPROC while traversing the queue whose lwWaitLink is NULL but which isn't > equal to > lock->tail. If that ever happens, we'd simply PANIC.
My current conclusion is that backporting barriers.h is by far the most reasonable way to go. The compiler problems have been ironed out by now... Arguments against? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
