Re: Back-patch use of unnamed POSIX semaphores for Linux?
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2016-12-07T20:22:56Z
Lists: pgsql-hackers
On Wed, Dec 7, 2016 at 3:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Tue, Dec 6, 2016 at 11:54 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> Robert Haas <robertmhaas@gmail.com> writes: >>>> On Tue, Dec 6, 2016 at 9:53 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>>>> I think we should give serious consideration to back-patching commit >>>>> ecb0d20a9, which changed the default semaphore type to unnamed-POSIX >>>>> on Linux. > >>>> Urk. That sounds like a scary thing to back-patch. > >>> I don't deny that it's scary, but the alternative seems to be to be >>> rather badly broken on systemd-using distros for years to come. >>> That's pretty scary too. > >> Why can't this be configurable? > > It already is. Note that I said "default". > > As things stand, it's only a configure-time choice, but I've been > thinking that we might be well advised to make it run-time configurable. Sure. A configure-time choice only benefits people who are compiling from source, which as far as production is concerned is almost nobody. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Make the different Unix-y semaphore implementations ABI-compatible.
- be7b2848c6d8 10.0 landed
-
Use unnamed POSIX semaphores, if available, on Linux and FreeBSD.
- ecb0d20a9d2e 10.0 cited