Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> This is probably overly restrictive; in fact, I would argue that there
>> should be no such check at all. We do not do runtime checks for
>> permissions on any other files, and some of them are far more sensitive
>> than postgresq
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Isn't the file in /data, which is 700. Why do we care what permissions
> we give it?
Indeed. I could understand having a postmaster-start-time check that
$PGDATA has mode 700 (initdb makes this true anyway, but having the
postmaster double-check is no
bonolin <[EMAIL PROTECTED]> writes:
> I install postgres 7.1 on solaris 2.6(sparc cpu).And create some
> db,runing normal.Today,I want to restart the database,it report
> "FATAL 1: configuration file `postgresql.conf' has wrong
> permissions",I check and change the permission to 775 ,but f
pgsql-bugs:
Hello!
I install postgres 7.1 on solaris 2.6(sparc cpu).And create some db,runing
normal.Today,I want to restart the database,it report "FATAL 1: configuration file
`postgresql.conf' has wrong permissions",I check and change the permission to 775 ,but
fail either,can you help.
