{"push_id":1339695551,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ecb0d20a9d2e09b7112d3b192047f711f9ff7e59","before":"ac4a9d92fcb6869e757cc729dca2ca5ccf94b185","commits":[{"sha":"ecb0d20a9d2e09b7112d3b192047f711f9ff7e59","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Use unnamed POSIX semaphores, if available, on Linux and FreeBSD.\n\nWe've had support for using unnamed POSIX semaphores instead of System V\nsemaphores for quite some time, but it was not used by default on any\nplatform.  Since many systems have rather small limits on the number of\nSysV semaphores allowed, it seems desirable to switch to POSIX semaphores\nwhere they're available and don't create performance or kernel resource\nproblems.  Experimentation by me shows that unnamed POSIX semaphores\nare at least as good as SysV semaphores on Linux, and we previously had\na report from Maksym Sobolyev that FreeBSD is significantly worse with\nSysV semaphores than POSIX ones.  So adjust those two platforms to use\nunnamed POSIX semaphores, if configure can find the necessary library\nfunctions.  If this goes well, we may switch other platforms as well,\nbut it would be advisable to test them individually first.\n\nIt's not currently contemplated that we'd encourage users to select\na semaphore API for themselves, but anyone who wants to experiment\ncan add PREFERRED_SEMAPHORES=UNNAMED_POSIX (or NAMED_POSIX, or SYSV)\nto their configure command line to do so.\n\nI also tweaked configure to report which API it's selected, mainly\nso that we can tell that from buildfarm reports.\n\nI did not touch the user documentation's discussion about semaphores;\nthat will need some adjustment once the dust settles.\n\nDiscussion: <8536.1475704230@sss.pgh.pa.us>","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/ecb0d20a9d2e09b7112d3b192047f711f9ff7e59"}]}
{"actor":{"display_login":"postgres-mirror"}}