| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Zeugswetter Andreas OSB sIT <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at>, Charlie Savage <cfis(at)savagexi(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |
| Date: | 2008-10-15 16:40:07 |
| Message-ID: | 23228.1224088807@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2008-10-15 16:45:58 | Re: autovacuum and reloptions |
| Previous Message | Alvaro Herrera | 2008-10-15 16:28:14 | Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED |