Gaetano Mendola wrote:
Vivek Khera wrote:
MTO == Matthew T O'Connor [EMAIL PROTECTED] writes:
Then it just sits there. I started it at 11:35am, and it is now
3:30pm.
MTO Weird Alphabetically speaking, is vkmlm.public.user_list
be the
MTO last table in the last schema in the last
Vivek Khera wrote:
MTO == Matthew T O'Connor [EMAIL PROTECTED] writes:
Then it just sits there. I started it at 11:35am, and it is now
3:30pm.
MTO Weird Alphabetically speaking, is vkmlm.public.user_list be the
MTO last table in the last schema in the last database? You are running
MTO == Matthew T O'Connor [EMAIL PROTECTED] writes:
MTO I don't run FreeBSD, so I haven't tested with FreeBSD. Recently Craig
MTO Boston reported and submitted a patch for a crash on FreeBSD, but that
some more debugging data:
(gdb) print now
$2 = {tv_sec = 1070565077, tv_usec = 216477}
(gdb)
MTO == Matthew T O'Connor [EMAIL PROTECTED] writes:
MTO I don't run FreeBSD, so I haven't tested with FreeBSD. Recently
Craig MTO Boston reported and submitted a patch for a crash on FreeBSD,
but that
some more debugging data:
(gdb) print now
$2 = {tv_sec = 1070565077, tv_usec = 216477}
MTO == Matthew T O'Connor [EMAIL PROTECTED] writes:
MTO Could this be the recently reported bug where time goes backwards on
MTO FreeBSD? Can anyone who knows more about this problem chime in, I know it
MTO was recently discussed on Hackers.
Time does not go backwards -- the now and then
Actually, you can simplify the fix thusly:
diff = (long long)(now.tv_sec - then.tv_sec) * 100 + (now.tv_usec -
then.tv_usec);
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
