From: | Steve Wampler <swampler(at)noao(dot)edu> |
---|---|
To: | John Hasler <jhasler(at)newsguy(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: What does PostgreSQL do when time goes backward? |
Date: | 2010-08-04 17:50:51 |
Message-ID: | 4C59A87B.1050005@noao.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
John Hasler wrote:
> Frank writes:
>> My ntp client changes clock (by small amount) at any time:
>> Jul 25 05:29:38 bax ntpd[10269]: adjusting local clock by 0.098724s
>> Jul 25 05:31:43 bax ntpd[10269]: adjusting local clock by 0.038991s
>> Jul 25 06:13:38 bax ntpd[10269]: adjusting local clock by -0.037131s
>> Jul 25 15:01:52 bax ntpd[10269]: adjusting local clock by -0.112429s
>
> Ken writes:
>> These do seem to be larger values than you might expect from a clock
>> conditioned with ntpd. Is it a VM or is there something going on that
>> would stop or suspend your system?
>
John writes:
> There is certainly something wrong there.
I saw very bad clock performance on one Linux box I had (dual-single core
AMD cpus, no VMs), even with NTP, until I changed the clocksource kernel
parameter to hpet. Unfortunately (or fortunately) I no longer have that box.
--
Steve Wampler -- swampler(at)noao(dot)edu
The gods that smiled on your birth are now laughing out loud.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Koczan | 2010-08-04 18:51:00 | Re: Domains, casts, and MS Access |
Previous Message | Richard Broersma | 2010-08-04 17:47:04 | Re: Domains, casts, and MS Access |