Robert Haas <robertmh...@gmail.com> wrote: > I've also added a lengthy README file to the patch that attempts > to explain how barriers should be used in PostgreSQL coding. It's > certainly not a comprehensive treatment of the topic, but > hopefully it's enough to get people oriented. I've attempted to > tailor it a bit to PostgreSQL conventions, like talking about > shared memory vs.backend-private memory instead of assuming (as a > number of other discussions of this topic do) a thread model. It > also includes some advice about when memory barriers shouldn't be > used or won't work, and some references for further reading. Thanks, that seems like it's at the right level of detail to me. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
