current_logfiles not following group access and instead follows log_file_mode permissions

From: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: current_logfiles not following group access and instead follows log_file_mode permissions
Date: 2019-01-15 04:08:41
Message-ID: CAJrrPGcEotF1P7AWoeQyD3Pqr-0xkQg_Herv98DjbaMj+naozw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

current_logfiles is a meta data file, that stores the current log writing
file, and this file
presents in the data directory. This file doesn't follow the group access
mode set at
the initdb time, but it follows the log_file_mode permissions.

without group access permissions, backup with group access can lead to
failure.
Attached patch fix the problem.

comments?

Regards,
Haribabu Kommi
Fujitsu Australia

Attachment Content-Type Size
0001-current_logfiles-file-following-group-access-mode.patch application/octet-stream 1.6 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-01-15 04:21:24 Re: unique, partitioned index fails to distinguish index key from INCLUDEd columns
Previous Message Peter Geoghegan 2019-01-15 04:02:57 Re: Safely calling index_getprocinfo() while holding an nbtree exclusive buffer lock