Re: Back-patch use of unnamed POSIX semaphores for Linux? - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: Back-patch use of unnamed POSIX semaphores for Linux?
Date
Msg-id CAFaPBrTFYV_mJyAMU0UY+vSz6KcQmzoD2va02nOD+GL9Uty-sw@mail.gmail.com
Whole thread Raw
In response to Re: Back-patch use of unnamed POSIX semaphores for Linux?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Back-patch use of unnamed POSIX semaphores for Linux?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Wed, Dec 7, 2016 at 1:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:


But this is all kind of moot if Peter is right that systemd will zap
POSIX shmem along with SysV semaphores.  I've been trying to reproduce
the issue on a Fedora 25 installation, and so far I can't get it to
zap anything, so I'm a bit at a loss how to prove things one way or
the other.


Don't know precisely about Fedora 25, but I've had success in the past with:
ssh in as the user
start postgres under tmux/screen
logout
do another ssh login/logout cycle

After logon, you should see "/usr/lib/systemd/systemd --user" running for that
user. After logout out, said proc should exit. If either of those is not true,
either systemd is not setup to track sessions (probably via pam) or it thinks
you still have an active logon. Another way to check if systemd thinks the user
is logged in is if /run/user/$USER exists.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Typmod associated with multi-row VALUES constructs
Next
From: Jim Nasby
Date:
Subject: Re: varlena beyond 1GB and matrix