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 C5DC4D1B8B7 for ; Fri, 16 Apr 2004 10:49:39 -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 15586-10 for ; Fri, 16 Apr 2004 10:49:39 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E4621D1B515 for ; Fri, 16 Apr 2004 10:49:37 -0300 (ADT) 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 i3GDncmY028604; Fri, 16 Apr 2004 09:49:38 -0400 (EDT) To: =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= Cc: josh@agliodbs.com, pgsql-performance@postgresql.org, Sven Geisler Subject: Re: RESOLVED: Re: Wierd context-switching issue on Xeon In-reply-to: <407FD9A0.6040608@aeccom.com> References: <200311251419.36771.josh@agliodbs.com> <200404150827.03950.josh@agliodbs.com> <407EB5B0.3030706@aeccom.com> <200404151039.17763.josh@agliodbs.com> <407EE93F.3090705@aeccom.com> <21280.1082064326@sss.pgh.pa.us> <407F9FE9.3060104@aeccom.com> <407FAF0F.2070304@aeccom.com> <407FD9A0.6040608@aeccom.com> Comments: In-reply-to =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= message dated "Fri, 16 Apr 2004 15:03:28 +0200" Date: Fri, 16 Apr 2004 09:49:38 -0400 Message-ID: <28603.1082123378@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/206 X-Sequence-Number: 6506 =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= writes: > This was the key to look at: we were missing all indices on table which > is used heavily and does lots of locking. After recreating the missing > indices the production system performed normal. No, more excessive > semop() calls, load way below 1.0, CS over 20.000 very rare, more in > thousands realm and less. Hmm ... that's darn interesting. AFAICT the test case I am looking at for Josh's client has no such SQL-level problem ... but I will go back and double check ... regards, tom lane