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

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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Jesse Morris <jmorris(at)coverity(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Date: 2009-11-16 08:30:28
Message-ID: 9837222c0911160030x18e8c6b6i4156f01ad05d3aa8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Mon, Nov 16, 2009 at 06:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> On Saturday, November 14, 2009, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> Not 8.2?
>
>> Done.
>
> Buildfarm member narwhal seems to think it's not quite right in 8.2.

Drat.

So, the new API function requires Windows 2000 or more, and I think
the reason it's failing is that the headers in 8.2 don't specify that
at this point. Which means that 8.2 today theoretically at least runs
on NT4. Which leads to the question - do we want to back out the
patch, have 8.2 keep working on that, and having 8.2 fail in the few
unusual scenarios we have now, or do we also backpatch the requirement
to run on win2k or later?


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

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2009-11-16 08:32:59
Subject: Re: [HACKERS] pgsql: /home/peter/commit-msg
Previous:From: Magnus HaganderDate: 2009-11-16 08:17:56
Subject: Re: [HACKERS] pgsql: /home/peter/commit-msg

pgsql-bugs by date

Next:From: Heikki LinnakangasDate: 2009-11-16 09:04:27
Subject: Multixact and prepared transactions
Previous:From: Tom LaneDate: 2009-11-16 05:23:21
Subject: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"

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