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 th
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 = timeG
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
Folks,
I've run into a problem affecting postgres on cygwin 1.5.7 (yes, we're
upgrading, but those things have to be scheduled and infrequent). We
have several systems that, after running for a month or two, will
exhibit the following symptom: "select now()" will start returning the
time at which
4 matches
Mail list logo
