Re: better atomics - v0.2
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Robert Haas <robertmhaas@gmail.com>,
Andres Freund <andres@2ndquadrant.com>, Peter Geoghegan <pg@heroku.com>,
Pg Hackers <pgsql-hackers@postgresql.org>, Ants Aasma <ants@cybertec.at>
Date: 2013-11-19T15:30:24Z
Lists: pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes: > On 11/19/13, 9:57 AM, Tom Lane wrote: >> Hm. Now that I think about it, isn't Peter proposing to break systems >> without working "inline" over here? >> http://www.postgresql.org/message-id/1384257026.8059.5.camel@vanquo.pezone.net > No, that's about const, volatile, #, and memcmp. Ah, sorry, not enough caffeine absorbed yet. Still, we should stop to think about whether this represents an undesirable move of the portability goalposts. The first three of these are certainly compiler issues, and I personally don't have a problem with blowing off compilers that still haven't managed to implement all of C89 :-(. I'm not clear on which systems had the memcmp issue --- do we have the full story on that? > I don't have an informed opinion about requiring inline support > (although it would surely be nice). inline is C99, and we've generally resisted requiring C99 features. Maybe it's time to move that goalpost, and maybe not. regards, tom lane
Commits
-
Avoid the use of a separate spinlock to protect a LWLock's wait queue.
- 008608b9d510 9.6.0 cited
-
Improve LWLock scalability.
- ab5194e6f617 9.5.0 cited
-
Reduce the number of semaphores used under --disable-spinlocks.
- daa7527afc22 9.4.0 cited
-
Alter the configure script to fail immediately if the C compiler does not
- d15cb38dec01 9.0.0 cited