Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
Date
Msg-id 20081015162814.GE6012@alvh.no-ip.org
Whole thread Raw
In response to Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED
List pgsql-hackers
Andrew Dunstan wrote:

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

Does it work for all backends to grab a lock, so that if they continue
to live after postmaster has died, then the new postmaster cannot start?

I guess the postmaster could try-acquire an exclusive lock and all other
processes would acquire a shared lock.

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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: autovacuum and reloptions
Next
From: Tom Lane
Date:
Subject: Re: 8.3 .4 + Vista + MingW + initdb = ACCESS_DENIED