> That sounds suspiciously close to the time from boot to wraparound of
> 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.
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
In response to
pgsql-hackers by date
|Next:||From: Joshua D. Drake||Date: 2006-08-31 22:34:21|
|Subject: Re: Win32 hard crash problem|
|Previous:||From: Tom Lane||Date: 2006-08-31 22:29:50|
|Subject: Re: updatable views and default values |