| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add doc advice about systemd RemoveIPC |
| Date: | 2017-02-10 21:36:30 |
| Message-ID: | 293b03d2-9d08-0ff8-4873-4ffe404eb9f6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/31/16 11:43 AM, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> I still think that some wording in the direction of the fact that the
>> majority of all users won't actually have this problem is the right thing
>> to do (regardless of our previous history in the area as pointed out by
>> Craig)
>
> +1. The use-a-system-user solution is the one that's in place on the
> ground for most current PG users on affected platforms. We should explain
> that one first and make clear that platform-specific packages attempt to
> set it up that way for you. The RemoveIPC technique should be documented
> as a fallback to be used if you can't/won't use a system userid.
How about this version, which shifts the emphasis a bit, as suggested?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-doc-Add-advice-about-systemd-RemoveIPC.patch | text/x-patch | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-02-10 21:36:53 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Peter Eisentraut | 2017-02-10 21:08:28 | Re: Add support to COMMENT ON CURRENT DATABASE |