Re: What to do when dynamic shared memory control segment is corrupt - Mailing list pgsql-general

From Alban Hertroys
Subject Re: What to do when dynamic shared memory control segment is corrupt
Date
Msg-id 0CA43180-0A86-4E3E-8637-56438A2FE36C@gmail.com
Whole thread Raw
In response to What to do when dynamic shared memory control segment is corrupt  (Sherrylyn Branchaw <sbranchaw@gmail.com>)
List pgsql-general
> On 18 Jun 2018, at 17:34, Sherrylyn Branchaw <sbranchaw@gmail.com> wrote:
>
> In the other case, the logs recorded
>
> LOG:  all server processes terminated; reinitializing
> LOG:  dynamic shared memory control segment is corrupt
> LOG:  incomplete data in "postmaster.pid": found only 1 newlines while trying to add line 7
>
> In that case, the database did not restart on its own. It was 5 am on Sunday, so the on-call SRE just manually
startedthe database up, and it appears to have been running fine since. 

That rings a bell. Some versions of systemd apparently clean up shared memory belonging to a user when it detects the
userlogs out. ISTR that we had to disable that on our CentOS 7 server to stop crashes from happening. 

More details here: https://wiki.postgresql.org/wiki/Systemd

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.



pgsql-general by date:

Previous
From: Łukasz Jarych
Date:
Subject: Re: Run Stored procedure - function from VBA
Next
From: Ron
Date:
Subject: Re: PostgreSQL Volume Question