Skip site navigation (1) Skip section navigation (2)

Re: Win32 hard crash problem

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win32 hard crash problem
Date: 2006-08-31 22:47:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)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?


    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-08-31 22:56:18
Subject: Re: Win32 hard crash problem
Previous:From: Tom LaneDate: 2006-08-31 22:39:36
Subject: Re: Win32 hard crash problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group