| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | Darcy Buskermolen <darcy(at)wavefire(dot)com>, "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: gettimeofday() goes backwards on FreeBSD 4.9 |
| Date: | 2003-11-29 01:08:31 |
| Message-ID: | 3507.1070068111@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> On Fri, 28 Nov 2003, Tom Lane wrote:
>> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> On an Intel Linux 2.4.18 I get them quite often, 25 in 1'45", but they
> are all just a microsecond.
>>
>> What do you mean by "just a microsecond"?
> I mean it's always a "out of order tv_usec..." line and the difference is
> 1us. That is a.out gives:
> out of order tv_usec: 1070065862 374978, prev 1070065862 374979
> out of order tv_usec: 1070065867 814300, prev 1070065867 814301
Fascinating. I'd call that a bug too, but evidently one with a
different mechanism than the BSD issue we are chasing.
FWIW, I have not seen any failures in a fair amount of runtime on
a 2.4.18 (Red Hat 8.0) kernel here, running on a Dell P4. What is
the hardware platform you're using?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-11-29 01:13:13 | Re: gettimeofday() goes backwards on FreeBSD 4.9 |
| Previous Message | Tom Lane | 2003-11-29 01:05:25 | Re: gettimeofday() goes backwards on FreeBSD 4.9 |