Re: current_logfiles not following group access and instead follows log_file_mode permissions
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Haribabu Kommi <kommi.haribabu@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Gilles Darold <gilles.darold@dalibo.com>
Date: 2019-03-22T01:23:54Z
Lists: pgsql-hackers
Attachments
- current-logfiles-perm-v4.patch (text/x-diff) patch v4
On Thu, Mar 21, 2019 at 12:52:14PM +1100, Haribabu Kommi wrote: > Earlier attached patch is wrong. - oumask = umask(pg_file_create_mode); + oumask = umask(pg_mode_mask); Indeed that was wrong. > Correct patch attached. Sorry for the inconvenience. This looks better for the umask setting, still it could be more simple. #include <sys/time.h> - +#include "common/file_perm.h" #include "lib/stringinfo.h" Nit: it is better for readability to keep an empty line between the system includes and the Postgres ones. A second thing, more important, is that you can reset umask just after opening the file, as attached. This way there is no need to reset the umask in all the code paths leaving update_metainfo_datafile(). Does that look fine to you? -- Michael
Commits
-
Make current_logfiles use permissions assigned to files in data directory
- 7d7435c5c505 11.3 landed
- 276d2e6c2d81 12.0 landed