On Tue, Feb 26, 2019 at 12:22:53PM +1100, Haribabu Kommi wrote: > I checked the code why the current_logfiles is not implemented as > shared memory and found that the current syslogger doesn't attach to > the shared memory of the postmaster. To support storing the > current_logfiles in shared memory, the syslogger process also needs > to attach to the shared memory, this seems to be a new > infrastructure change.
I don't think you can do that anyway and we should not do it. Shared memory can be reset after a backend exits abnormally, but the syslogger lives across that. What you sent upthread to improve the documentation is in my opinion sufficient: https://www.postgresql.org/message-id/cajrrpge-v2_lmfd9nhrbejjy3vvokjwy3w_h+fs2nxcjg3p...@mail.gmail.com I would not have split the paragraph you broke into two, but instead just add this part in-between: + <para> + Permissions <literal>0640</literal> are recommended to be compatible with + <application>initdb</application> option <option>--allow-group-access</option>. + </para> Any objections in doing that? -- Michael
signature.asc
Description: PGP signature
