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 86381D1B262 for ; Thu, 20 May 2004 02:11:14 -0300 (ADT) 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 75008-03 for ; Thu, 20 May 2004 02:10:55 -0300 (ADT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 0F641D1B28B for ; Thu, 20 May 2004 02:10:54 -0300 (ADT) Received: from ool-4352919e.dyn.optonline.net ([67.82.145.158] helo=[192.168.1.10]) by outbound.mailhop.org with asmtp (Exim 4.20) id 1BQfow-000FWV-SE; Thu, 20 May 2004 01:10:18 -0400 Subject: Re: Wierd context-switching issue on Xeon From: "Matthew T. O'Connor" To: Robert Creager Cc: Bruce Momjian , pg@fastcrypt.com, Josh Berkus , =?ISO-8859-1?Q?Dirk=5FLutzeb=E4ck?= , ohp@pyrenet.fr, Tom Lane , Joe Conway , "scott.marlowe" , pgsql-performance@postgresql.org, Neil Conway In-Reply-To: <20040519195926.3c5fa3bc@thunder.mshome.net> References: <1083512362.25096.131.camel@localhost.localdomain> <200405200120.i4K1KKm06350@candle.pha.pa.us> <20040519195926.3c5fa3bc@thunder.mshome.net> Content-Type: text/plain Message-Id: <1085029814.32765.10.camel@zedora2> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 20 May 2004 01:10:14 -0400 Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 67.82.145.158 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: Zeut X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_NJABL, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/168 X-Sequence-Number: 6999 On Wed, 2004-05-19 at 21:59, Robert Creager wrote: > When grilled further on (Wed, 19 May 2004 21:20:20 -0400 (EDT)), > Bruce Momjian confessed: > > > > > Did we ever come to a conclusion about excessive SMP context switching > > under load? > > > > I just figured out what was causing the problem on my system Monday. I'm using > the pg_autovacuum daemon, and it was not vacuuming my db. I've no idea why and > didn't get a chance to investigate. Strange. There is a known bug in the 7.4.2 version of pg_autovacuum related to data type mismatches which is fixed in CVS. But that bug doesn't cause pg_autovacuum to stop vacuuming but rather to vacuum to often. So perhaps this is a different issue? Please let me know what you find. Thanks, Matthew O'Connor