current_logfiles not following group access and instead followslog_file_mode permissions - Mailing list pgsql-hackers

From Haribabu Kommi
Subject current_logfiles not following group access and instead followslog_file_mode permissions
Date
Msg-id CAJrrPGcEotF1P7AWoeQyD3Pqr-0xkQg_Herv98DjbaMj+naozw@mail.gmail.com
Whole thread Raw
Responses Re: current_logfiles not following group access and instead followslog_file_mode permissions  (Michael Paquier <michael@paquier.xyz>)
List 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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Safely calling index_getprocinfo() while holding an nbtreeexclusive buffer lock
Next
From: Alvaro Herrera
Date:
Subject: Re: unique, partitioned index fails to distinguish index key fromINCLUDEd columns