Great! I was going to start work on a fix, too, but ran into cygwin building problems, so you beat me to it. Thanks!
I have the snapshot running. And postgres is keeping time. I haven't looked at your source yet, but I assume there's still an independent counter running and you're resetting the base time it counts from. If this is so, I don't really have a way to test the wrap-around other than to let it run for 50 days and see if it works. :) On Thu, 2004-07-01 at 07:37, Corinna Vinschen wrote: > On Jun 28 23:04, Sean McCune wrote: > > More useful info: (and yes I'm replying to my own message) > > > > I spelunked through the source code and found this in times.cc: > > > > LONGLONG > > hires_ms::usecs (bool justdelta) > > { > > if (!minperiod) /* NO_COPY variable */ > > prime (); > > DWORD now = timeGetTime (); > > // FIXME: Not sure how this will handle the 49.71 day wrap around > > LONGLONG res = initime_us.QuadPart + ((LONGLONG) (now - initime_ms) * > > 1000); > > return res; > > } > > I've checked in a potential fix. Could you try the latest Cygwin snapshot > from http://cygwin.com/snapshots.html ? > > Thanks, > Corinna -- Sean McCune Red Hand Software, Inc. [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/