<br /><blockquote type="CITE"><pre>
<font color="#000000">That's not workable, unless you want to assume that nothing on the</font>
<font color="#000000">system except Postgres uses SysV semaphores. Otherwise something else</font>
<font color="#000000">could randomly gobble up the semid you want to use. I don't care very</font>
<font color="#000000">much for requiring a distinct semid to be hand-specified for each</font>
<font color="#000000">postmaster on a machine, either. </font>
</pre></blockquote><br /> Yeah, that does suck. Ok, naming problems seem to make semaphores useless.<br /><br /> I'm
backto byte-range locking, but if NFS is important and is truly unreliable, then that's out too.<br /><br /> I've never
hadlocking problems on NFS (probably because we tell our users not to use NFS), but now that I think about it, SMB
lockingis very unreliable so Win32 would be an issue too.<br /><br /> -- Korry<br /><br />
