Re: Socket problem using beta2 on Windows-XP - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Socket problem using beta2 on Windows-XP
Date
Msg-id 20051002151223.GH30492@svana.org
Whole thread Raw
In response to Re: Socket problem using beta2 on Windows-XP  (Thomas Hallgren <thhal@mailblocks.com>)
List pgsql-hackers
On Sun, Oct 02, 2005 at 12:20:05PM +0200, Thomas Hallgren wrote:
> I added some traces to the code. I know that the following happens when
> I start a postmaster.

<snip>

> In the second iteration of ServerLoop, pgstat_forkexec will again call
> will call internal_fork_exec. This time it fails.
> According to the log it fails on line:
>
>    write_inheritable_socket(¶m->pgStatSock, pgStatSock, childPid);

Well, pgStatSock is the only SOCK_DGRAM socket, all the others are
SOCK_STREAM, maybe that's the difference? It's also connected to
itself, although for DGRAM sockets that's not that special.

The documentation isn't totally clear about this. Yet the error thrown
should terminate the process, yet it obviously isn't. Very odd.

Any Windows programmers with ideas?
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 8.1beta2 pg_dumpall inconsistencies
Next
From: Greg Stark
Date:
Subject: Re: effective SELECT from child tables