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: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Date
Msg-id 9837222c0911160030x18e8c6b6i4156f01ad05d3aa8@mail.gmail.com
Whole thread Raw
In response to 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: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
On Mon, Nov 16, 2009 at 06:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>>> On Saturday, November 14, 2009, Tom Lane <tgl@sss.pgh.pa.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/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Next
From: Heikki Linnakangas
Date:
Subject: Multixact and prepared transactions