Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2 - Mailing list pgsql-general

From Magnus Hagander
Subject Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2
Date
Msg-id 465C9A4A.4020600@hagander.net
Whole thread Raw
In response to [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2  ("Cyril VELTER" <cyril.velter@metadys.com>)
Responses [Re] Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2
Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2
List pgsql-general
Cyril VELTER wrote:
>     OK, I've the results of my tests :
>
>     With the previous code, then message "SOCKERROR" is printed 5 times during the
> whole process (100 Gb dump import with psql). There one group of three and one
> group of two, but I don't have timestamps and am not sure if they are printing
> in the same loop or not. The import is finally successful.

Ok.


>     The second test I have done is to remove FD_ACCEPT I still have the message
> one times, but it still happen. The import is also sucessfull.

Ok. So FD_ACCEPT is not the fix. Good, I didn't think it would be.


>> I'm also a bit worried about it getting caught in a tight loop if the
>> error codes are wrong, but probably it just goes back into waitfor.. and
>> blocks the second time. Otherwise, you'd see screenfuls of that message.
>>
>> Can you determine if it was hit two times right after each other, or if
>> there was time between them?
>
>     For the first test I don't known the amount of time between them (I have two
> groups separeted in the logs with other messages).

Ok. I'm thinking of just sticking a minimal wait in there to protect
against absolute runaway, but that should be enough I think.


>     What do you think ? may be a bug in the windows server installation I have
> (this machines have not been updated for some times, perhaps I should try to do
> that and see if the problem is still there. In the long run, I plan to upgrade
> to windows 2003).

I don't *think* it should be a bug with your version, it doesn't look
like it. but if you're not on the latest service pack, that's certainly
possible. Please update to latest servicepack + updates from Windows
Update / WSUS, and let me know if the problem persists.

Meanwhile, I'll try to cook up a patch.

//Magnus

pgsql-general by date:

Previous
From: "John D. Burger"
Date:
Subject: Re: Geographic data sources, queries and questions
Next
From: "Diego Fernando Arce"
Date:
Subject: monitor stats