Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cEyzo-0002rH-Ud for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Dec 2016 13:44:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cEyzo-0001q2-IN for pgsql-hackers@arkaria.postgresql.org; Thu, 08 Dec 2016 13:44:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cEyzo-0001pw-4V for pgsql-hackers@postgresql.org; Thu, 08 Dec 2016 13:44:24 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cEyzl-00032m-L1 for pgsql-hackers@postgresql.org; Thu, 08 Dec 2016 13:44:23 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 856C020879; Thu, 8 Dec 2016 08:44:19 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 08 Dec 2016 08:44:19 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=X+AC3SzvRhqumuoQPf8xKKd0sgs=; b=k6V8tmRVJiOhkt4Ff5ha 3uWffuD4ce21jmAI6e8ERTxeVfJkXe2xjKJDd5J5+M5WOTqgq5JnV2C/YaU86dq3 ACWI3pNEETUts/IjNsiDT/oMWeqBiAP49+5PIwP+SIGE0QUxwfKueuWO5H0/2WeO QFEH8AdTynWscIQctcUia9M= X-ME-Sender: X-Sasl-enc: /vLpAzAeEYA2CHjQueSaIL9NjspvPNpYaPyUHYCC90tp 1481204659 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 407777E8C3; Thu, 8 Dec 2016 08:44:19 -0500 (EST) Subject: Re: Back-patch use of unnamed POSIX semaphores for Linux? To: Alex Hunsaker , Tom Lane References: <32387.1481079186@sss.pgh.pa.us> <4886.1481086483@sss.pgh.pa.us> <27282.1481141564@sss.pgh.pa.us> <32665.1481150572@sss.pgh.pa.us> Cc: Robert Haas , "pgsql-hackers@postgresql.org" From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <589cde75-0d41-52b7-74bc-a1069bba967b@2ndquadrant.com> Date: Thu, 8 Dec 2016 08:44:18 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 12/7/16 9:28 PM, Alex Hunsaker wrote: > Hrm, the following incantation seems to break for me on a fresh Fedora > 25 system: > 1) As root su to $USER and start postgres. > 2) ssh in as $USER and then logout > 3) # psql localhost > > FATAL: semctl(4980742, 3, SETVAL, 0) failed: Invalid argument > LOG: server process (PID 14569) exited with exit code 1 Yeah, the way to trigger this is to run the postgres server not in a "session", then log in interactively as that same user, thus creating a session, and then logging out from that session, thus completely logging out that user from all sessions. (Thus, the way to trigger the KillUserProcesses behavior is quite the opposite, because that only happens if you have the postgres server running in a session.) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers