Socket problem using beta2 on Windows-XP

[Thomas Hallgren <thhal(at)mailblocks(dot)com>]

Hi,
I've installed PostgreSQL 8.1-beta2 as a service on my Windows-XP box. 
It runs fine but I get repeated messages like this in the log:

  2005-09-29 00:41:09 FATAL:  could not duplicate socket 1880 for use 
in backend: error code 10038

and for each message printed, a new postgres process is created. To make 
things worse, those processes do not die when I stop the service.

I use sysinternals tcpview to monitor my sockets. I know that no other 
process is using 1880. Each started postgres process will occupy two, 
seemingly random ports that apparently form a loop somehow. This is a 
typical entry:

  <non-existent>:3136	TCP	127.0.0.1:1554	127.0.0.1:1555 ESTABLISHED	
  <non-existent>:3136	TCP	127.0.0.1:1555	127.0.0.1:1554	ESTABLISHED	

The weird thing is that there is no process with pid 3136 (hence the 
name <non-existent>). There is a postgres process with another pid in my 
process listing. If I kill that, the <non-existstent> entries go away.

Looks like pid 3136 is talking to itself. A pipe() followed by failure 
to start the new process perhaps?

Regards,
Thomas Hallgren