Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
От | Tom Lane |
---|---|
Тема | Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" |
Дата | |
Msg-id | 1899.1256057128@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"
Re: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable" |
Список | pgsql-bugs |
Dave Page <dpage@pgadmin.org> writes: > On Tue, Oct 20, 2009 at 3:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Do we have any idea why? > Honestly? No. I have a vague hand-wavy idea about there being > something preventing us properly modifying the token of an existing > process in some configurations, but nothing even remotely jello-like, > let alone concrete. After re-reading the thread I am struck by Jesse's comment that the current coding never worked at all for him. It seems like that must indicate an environment difference or installed-software difference compared to the setups where it does work. (Antivirus maybe?) Seems like it would be worth the trouble to identify exactly what the critical difference is. regards, tom lane
В списке pgsql-bugs по дате отправления: