Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Date
Msg-id 4E79EB210200002500041576@gw.wicourts.gov
Whole thread Raw
In response to Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> wrote:
> But even a full explanation of that case seems like almost too
> much for the comment of a header file, and there are certainly far
> more complex cases.  I think anyone who is using these primitives
> is going to have to do some independent reading...
Maybe a URL or two in the header comments, pointing to relevant
papers for the techniques used?  After all, years from now someone
might be familiar with other techniques from newer papers and wonder
what the techniques in the code are based on.
-Kevin


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Next
From: Merlin Moncure
Date:
Subject: Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?