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

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Дата
Msg-id 20091116212016.GH3669@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Magnus Hagander wrote:

> 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?

I think the safest course is to revert the fix and keep 8.2 working on
all platforms on which it used to work.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5192: --disable-integer-datetimes changes timestamp comparison behavior
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"