Re: BUG #13818: PostgreSQL crashes after cronjob runs as "postgres"

From: Ryan Park <ryan(at)runscope(dot)com>
To: Alexey Lesovsky <lesovsky(at)pgco(dot)me>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13818: PostgreSQL crashes after cronjob runs as "postgres"
Date: 2016-01-12 18:15:56
Message-ID: CAJtUy-0FhQPYPQoPPfkc9noAAWCQ3N4L+2CttrbdiiPvJwVumw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Alexey -- thank you so much for pointing us in the right direction. We
followed your instructions and it allowed us to run cron jobs as the
"postgres" user again.

Ryan Park
Runscope Operations

On Sat, Jan 9, 2016 at 8:45 AM, Alexey Lesovsky <lesovsky(at)pgco(dot)me> wrote:

> Hi,
>
> Check installed systemd version, since 212 systemd has "cool feature".
> Particilarly, systemd-logind process automatically removes all IPC objects
> owned by a user if she or he fully logs out.
> Set "RemoveIPC=no" in /etc/systemd/logind.conf ans restart systemd-logind
> service to disable this.
>
> Regards, Alexey Lesovsky.
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message roman.vanicek 2016-01-12 19:42:25 BUG #13861: Database dump does not load when both plpython2u and plpython3u functions are used
Previous Message Frik Brits 2016-01-12 11:46:21 permissions.