X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8DA47D1CCA8 for ; Fri, 30 Jan 2004 22:40:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 40441-09 for ; Fri, 30 Jan 2004 18:40:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id DEEFDD1D105 for ; Fri, 30 Jan 2004 18:40:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0UMeTYI020420; Fri, 30 Jan 2004 17:40:29 -0500 (EST) To: David Teran Cc: Stephan Szabo , PgSQL Performance ML Subject: Re: another query optimization question In-reply-to: <07461B1A-5370-11D8-9392-000A95A6F0DC@cluster9.com> References: <32DEEB93-534E-11D8-9392-000A95A6F0DC@cluster9.com> <20040130100845.E58632@megazone.bigpanda.com> <17545.1075490366@sss.pgh.pa.us> <07461B1A-5370-11D8-9392-000A95A6F0DC@cluster9.com> Comments: In-reply-to David Teran message dated "Fri, 30 Jan 2004 23:02:43 +0100" Date: Fri, 30 Jan 2004 17:40:29 -0500 Message-ID: <20419.1075502429@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/336 X-Sequence-Number: 5510 David Teran writes: >> I recall that we saw similar symptoms once before, and I thought we'd >> fixed it, but I didn't find any relevant mentions in the CVS logs. >> >> What version are you running, exactly? > 7.4.1, build from sourcecode. Running on MacOS X Server 10.3.2, dual G5 > with 3.5 GB RAM Interesting. I have recollected where we saw this before: http://archives.postgresql.org/pgsql-hackers/2003-11/msg01528.php Apparently gettimeofday() has a glitch on some BSD releases. OS X is a BSD derivative and it's not so surprising if it has it too. May I suggest that you try the test program given here: http://archives.postgresql.org/pgsql-hackers/2003-11/msg01546.php and file a bug report with Apple if it shows any out-of-order results? I am fairly certain that I tried that test program when I devised it on my own OS X machine, and couldn't get a failure. Maybe it depends on your hardware (hm, could dual CPUs be the key factor)? regards, tom lane