Re: Win32 hard crash problem

Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>>> My bet is something depending on GetTickCount to measure elapsed time
>>> (and no, it's not used in the core Postgres code, but you've got plenty
>>> of other possible culprits in that stack).
> 
>> This doesn't quite make sense. The only reason we have to reboot is 
>> because PostgreSQL no longer responds. The system itself is fine.
> 
> The Windows kernel may still work, but that doesn't mean that everything
> Postgres depends on still works.  I'm wondering about (a) the TCP stack
> (and that includes 3rd party firewalls and such, not only the core
> Windows code); (b) timing or threading stuff inside the application
> that's using libpq, which the only thing we know about so far is that
> it's *not* JDBC/Hibernate.

/me grumbles in a not so polite way about Windows.

Which means we need to start stripping it down. Gah, I actually argued 
*for* this port to. Next time slap me.

Joshua D. Drake


> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq
> 


-- 
   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240   Providing the most comprehensive  PostgreSQL
solutionssince 1997             http://www.commandprompt.com/