From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add doc advice about systemd RemoveIPC |
Date: | 2017-02-15 15:56:25 |
Message-ID: | 88f5c2c2-fada-d436-a8d4-7f47fcd7a50f@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/14/17 11:49 AM, Magnus Hagander wrote:
> + <para>
> + If <productname>systemd</productname> is in use, some care must be
> taken
> + that IPC resources (shared memory and semaphores) are not prematurely
> + removed by the operating system. This is especially of concern when
> + installing PostgreSQL from source. Users of distribution packages of
> + PostgreSQL are less likely to be affected.
> + </para>
>
> I would add "are less likely to be affected as the postgres user is
> normally created as a system user" or something like that -- to indicate
> *why* they are less likely to be affected (and it also tells people that
> if they change the user, then they might become affected again).
Committed with that addition, thanks!
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-02-15 16:08:08 | Re: [Bug fix] PQsendQuery occurs error when target_session_attrs is set to read-write |
Previous Message | Robert Haas | 2017-02-15 15:52:03 | Re: pg_basebackup -R |