Never mind. Turns out the bug was in our own code (read: me,
personally, being stupid) to convert a java.sql.Timestamp to
java.sql.Date. Why it works at all in MySQL... I don't even want to
know.
Why is it we can spend weeks looking at a bug, and we can't find it
until we decide to blame it on someone else?
David
On Jun 10, 2009, at 11:58 AM, Tom Lane wrote:
"David Leppik" <dlep...@vocalabs.com> writes:
We are intermittently getting results from now() which are around
10 minutes
in the future. Most calls return a reasonable value. Because the
erroneous
timestamps are in the future, they cannot be explained by transaction
delays.
Postgres is just reporting what it got from gettimeofday(), so your
beef
is with the kernel (or perhaps with glibc) and/or the hardware you're
using. I think I've heard of kernel bugs causing this type of issue.
regards, tom lane
--
David Leppik
VP of Software Development
Vocal Laboratories, Inc.
dlep...@vocalabs.com
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
