Re: [HACKERS] compiler barriers (was: New statistics for WAL buffer dirty writes)

2012-08-31 Thread Bruce Momjian
Was there any conclusion from these ideas? --- On Wed, Aug 1, 2012 at 11:35:56AM -0400, Robert Haas wrote: > On Wed, Aug 1, 2012 at 10:12 AM, Tom Lane wrote: > > I think you may be right that using __asm__ __volatile__ in

Re: [HACKERS] compiler barriers (was: New statistics for WAL buffer dirty writes)

2012-08-01 Thread Robert Haas
On Wed, Aug 1, 2012 at 10:12 AM, Tom Lane wrote: > I think you may be right that using __asm__ __volatile__ in gcc > S_UNLOCK cases would be a big step forward, but it needs more research > to see if that's the only fix needed. Looking through the spinlock implementations in s_lock.h, we start wi