> 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 ?
pgsql-hackers by date
|Next:||From: Horst Herb||Date: 2000-11-29 08:51:43|
|Subject: Re: beta testing version|
|Previous:||From: Larry Rosenman||Date: 2000-11-29 05:16:34|
|Subject: Re: Re: LOCK Fixes/Break on FreeBSD 4.2-STABLE|