| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs) |
| Date: | 2011-09-14 20:29:31 |
| Message-ID: | CA+Tgmoah7-1QR4k7kTimT=qvuB6yBS0u5SqC2nP5y=WzieZNDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 8, 2011 at 7:47 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I've been thinking about this too and actually went so far as to do
> some research and put together something that I hope covers most of
> the interesting cases. The attached patch is pretty much entirely
> untested, but reflects my present belief about how things ought to
> work.
And, here's an updated version, with some of the more obviously broken
things fixed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| barrier-v2.patch | application/octet-stream | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Kupershmidt | 2011-09-14 22:22:59 | Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ... |
| Previous Message | Josh Berkus | 2011-09-14 20:15:21 | Re: What Would You Like To Do? |