Re: Spinlocks and compiler/memory barriers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Spinlocks and compiler/memory barriers
Date
Msg-id 456.1410185278@sss.pgh.pa.us
Whole thread Raw
In response to Re: Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Spinlocks and compiler/memory barriers
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-09-04 14:19:47 +0200, Andres Freund wrote:
>> Yes. I plan to push the patch this weekend. Sorry for the delay.

> I'm about to push this. Is it ok to first push it to master and only
> backpatch once a couple buildfarm cycles haven't complained?

It makes for a cleaner commit history if you push concurrently into
all the branches you intend to patch.  That also gives more buildfarm
runs, which seems like a good thing for this sort of patch.

That is, assuming that we ought to backpatch at all, which to my mind
is debatable.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: add modulo (%) operator to pgbench
Next
From: Robert Haas
Date:
Subject: Re: Spinlocks and compiler/memory barriers