Re: [bug fix] pg_ctl fails with config-only directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "MauMau" <maumau307(at)gmail(dot)com>
Cc: "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "Christian Kruse" <christian(at)2ndQuadrant(dot)com>, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] pg_ctl fails with config-only directory
Date: 2014-04-05 00:35:23
Message-ID: 13892.1396658123@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"MauMau" <maumau307(at)gmail(dot)com> writes:
> From: "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-04-05 02:12:31 Re: [bug fix] pg_ctl fails with config-only directory
Previous Message Tom Lane 2014-04-05 00:10:16 Re: [bug fix] "pg_ctl stop" times out when it should respond quickly