Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
| От | Tom Lane |
|---|---|
| Тема | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |
| Дата | |
| Msg-id | 23228.1224088807@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |
| Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes:
> I have verified that it does indeed work. Underneath the hood it uses
> the native call LockFileEx() see win32io.c in Perl source. I suggest we
> should switch from this flaky use of Global namespace to having the
> postmaster acquire an explicit lock on a file in the datadir.
That can only be a solution if postmaster child processes will inherit
the lock. (The nasty scenario is where the postmaster has died but one
or more backends are still alive --- a new postmaster attempting to
start MUST detect that and refuse to start.) Does fork/exec preserve
lock ownership on Windows?
regards, tom lane
В списке pgsql-hackers по дате отправления: