Re: [bug fix] pg_ctl fails with config-only directory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [bug fix] pg_ctl fails with config-only directory
Date
Msg-id 13892.1396658123@sss.pgh.pa.us
Whole thread Raw
In response to Re: [bug fix] pg_ctl fails with config-only directory  ("MauMau" <maumau307@gmail.com>)
Responses Re: [bug fix] pg_ctl fails with config-only directory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"MauMau" <maumau307@gmail.com> writes:
> From: "Heikki Linnakangas" <hlinnakangas@vmware.com>
>> Hmm, why do this only on Windows? If "postgres -C" is safe enough to run 
>> as Administrator on Windows, why not allow running it as root on Unix as 
>> well? Even if there's no particular need to allow it as root on Unix, 
>> fewer #ifdefs is good.

> Yes, I limited the change only to Windows, because I thought I might get get 
> objection against unnecessary change.  Plus, --single should not be allowed 
> for root, because root cannot be the PostgreSQL user account.

Indeed, and why would that not apply to Windows as well?  AFAIK, inclusion
of --single in this list is just plain nuts.  The most likely result of
running that way is creation of root-owned files inside $PGDATA, which
would cause havoc for later normally-privileged postmasters.

I will go and commit this, without the #ifdefs and without the --single
exclusion.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [bug fix] "pg_ctl stop" times out when it should respond quickly
Next
From: Tom Lane
Date:
Subject: Re: [bug fix] pg_ctl fails with config-only directory