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 59B0CD1D5E4 for ; Sat, 31 Jan 2004 15:48:37 +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 54427-10 for ; Sat, 31 Jan 2004 11:48:38 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 5B355D1D5B2 for ; Sat, 31 Jan 2004 11:48:34 -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 i0VFjunp003876; Sat, 31 Jan 2004 10:45:56 -0500 (EST) To: David Teran Cc: Stephan Szabo , Marc Fournier , PgSQL Performance ML Subject: Re: another query optimization question In-reply-to: <39D3D2E6-53D8-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> <20419.1075502429@sss.pgh.pa.us> <39D3D2E6-53D8-11D8-9392-000A95A6F0DC@cluster9.com> Comments: In-reply-to David Teran message dated "Sat, 31 Jan 2004 11:28:35 +0100" Date: Sat, 31 Jan 2004 10:45:56 -0500 Message-ID: <3875.1075563956@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/347 X-Sequence-Number: 5521 David Teran writes: > Apple provides a little tool that can enable / disable the l2 cache ... > one CPU of a dual CPU system on the fly. When i start the testapp with > two CPU's enabled i get this output here, when i turn off one CPU while > the app is still running the messages disappear as long as one CPU is > turned off. Reactivating the CPU again produces new error messages. Ah-hah, so the gettimeofday bug *is* linked to multiple CPUs. Marc, were the machines you saw it on all multi-CPU? > Do you remember where one can find a patch? File a bug report with Apple. > Do you know if this bug makes a system unusable with PostgresSQL? Not at all. The only bad effect we've noted is that EXPLAIN results are sometimes wacky. In theory you could sometimes see the result of now() being off by a second or two, but no one's reported seeing that. regards, tom lane