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

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "Christian Kruse" <christian(at)2ndQuadrant(dot)com>
Cc: "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-02-20 11:55:15
Message-ID: 27B1B4DF2D044EC4B555DD8372A02F30@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marti Raudsepp 2014-02-20 11:58:00 Re: Selecting large tables gets killed
Previous Message Ashutosh Bapat 2014-02-20 11:06:46 Re: Priority table or Cache table