Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Date
Msg-id 9837222c0910210702u1592035bn2c45eb92ee76ce6d@mail.gmail.com
Whole thread Raw
In response to Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
List pgsql-bugs
On Wed, Oct 21, 2009 at 15:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dave Page <dpage@pgadmin.org> writes:
>> This function call is adding the new access control entry to the DACL,
>> and in Jesse's modified version it's specifying that the ACE should be
>> inheritable.
>
> Hah, so now we have a theory.
>
>> The other refactoring is still important however - without it, I still
>> see the error. I would guess that you cannot add an inheritable ACE
>> once the process has been created, but I cannot say for certain.
>
> That would make sense if the state gets copied to the process at time
> of creation. =A0Okay, I'm satisfied that this is a believable patch...

=46rom a quick look, it looks fine to me. I don't have time to do a
complete check right now, but I'll do that as soon as I can and then
commit it - unless people feel it's more urgent than maybe a week
worst case, in which case someone else has to pick it up :-)


--=20
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Next
From: Andrew Dunstan
Date:
Subject: Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"