Re: AW: F_SETLK is looking worse and worse... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: F_SETLK is looking worse and worse...
Date
Msg-id 27475.975513450@sss.pgh.pa.us
Whole thread Raw
In response to AW: F_SETLK is looking worse and worse...  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at> writes:
>> BTW, it also seems like a good idea to reorder the postmaster's
>> startup operations so that the data-directory lockfile is checked
>> before trying to acquire the port lockfile, instead of after.  That
>> way, in the common scenario where you're trying to start a second
>> postmaster in the same directory + same port, it'd fail cleanly
>> even if /tmp/.s.PGSQL.5432.lock had disappeared.

> Fine, sounds like reordering would eliminate the need for the socket lock 
> anyway, no ?

Not at all.  If you start two postmasters in different data directories
but with the same port number, you still have a socket-file conflict
that needs to be detected.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: F_SETLK is looking worse and worse...
Next
From: Peter Eisentraut
Date:
Subject: Re: Initdb not running on beos