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 9837222c0911191728y7de9bc63q9749957bac427017@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>)
List pgsql-bugs
2009/11/16 Tom Lane <tgl@sss.pgh.pa.us>:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> Magnus Hagander wrote:
>>> 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?
>
>> I think the safest course is to revert the fix and keep 8.2 working on
>> all platforms on which it used to work.
>
> +1 --- since this seems to be a corner case, desupporting old Windows
> versions in a minor update doesn't seem like the thing to do.

Agreed, reverted.


> Sorry for creating work for you, Magnus.

No problem.


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

pgsql-bugs by date:

Previous
From: "Andrew Masterton"
Date:
Subject: BUG #5200: Use of min suffix in autovacuum_naptime ignored
Next
From: Robert Haas
Date:
Subject: Re: BUG #5197: JDBC: selecting oid results in Exception