Skip site navigation (1) Skip section navigation (2)

Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Jesse Morris <jmorris(at)coverity(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Date: 2009-10-16 09:13:46
Message-ID: 937d27e10910160213n5c2bb01bpd8a46c870fff4bbb@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Fri, Oct 16, 2009 at 1:08 AM, Jesse Morris <jmorris(at)coverity(dot)com> wrote:

> I went back to the version that supposedly initially fixed this issue,
> but I couldn't get it to work either.  So I think the DACL adjustment
> code was always broken.  The DACL stuff that both Cygwin and Active
> Perl use to simulate *nix file permissions masks this error, so any
> test framework that uses them would get false negatives on this bug.
> Since these DACLs are inheritable, a workaround is to run pg_ctl as a
> child process of Active Perl or Cygwin.   The comments indicated
> pg_ctl & initdb were already trying to do the same thing themselves
> (that is, add the current user to the DACLs) but it didn't actually
> work on any of the systems I tried it on.

In fairness it wasn't entirely broken as it fixed the problem for the
majority of people. Clearly there's room for improvement though as we
do still see the problem occasionally.

> I think that a number of other people have seen this bug; search for
> "FATAL: postgres - could not locate matching postgres executable."
> But that message is so misleading is probably why it seems nobody has
> properly diagnosed it as a permissions issue before.  I didn't do
> anything to fix pg_ctl's error reporting.  :D

We figured out that it was a permissions problem after a *lot* of back
and forth with Microsoft's developer support engineers - that's what
led to the AddUserToDacl fix. What didn't then happen was further
investigation into the handful of later reports of similar issues -
unfortunately that can be extremely difficult as few users are
experienced Windows programmers. It's great to see someone that is has
seen the problem and taken the time to figure it out :-).

> The patch:
>
> ------begin patch------

:-(. Unfortunately inlining the patch in the email has munged it
beyond usability. Can you resend it as an attachment please?

Thanks!

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2009-10-16 09:37:10
Subject: Re: Reworks for Access Control facilities (r2363)
Previous:From: Simon RiggsDate: 2009-10-16 08:31:41
Subject: Re: Trigger with WHEN clause (WIP)

pgsql-bugs by date

Next:From: Thom BrownDate: 2009-10-16 09:55:46
Subject: vacuumdb error
Previous:From: AndreyDate: 2009-10-16 07:54:39
Subject: BUG #5123: bug in window function "last_value"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group