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:29:52
Message-ID: 44F762E0.2080001@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> 
> That sounds suspiciously close to the time from boot to wraparound of
> GetTickCount:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/gettickcount.asp
> M$ list this as 49 days but that's the time to wrap clear around to
> zero; the value overflows and goes negative in 24.85 days if I've
> done the math correctly.
> 
> 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.

Sincerely,

Joshua D. Drake


-- 

    === 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
              http://www.commandprompt.com/



In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2006-08-31 22:34:21
Subject: Re: Win32 hard crash problem
Previous:From: Tom LaneDate: 2006-08-31 22:29:50
Subject: Re: updatable views and default values

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