Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 3C2A09FB432 for ; Thu, 26 Jul 2007 12:43:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 57091-01 for ; Thu, 26 Jul 2007 12:43:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E4E519FB422 for ; Thu, 26 Jul 2007 12:43:16 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6QFgnJW027578; Thu, 26 Jul 2007 11:42:49 -0400 (EDT) To: "Jignesh K. Shah" cc: Simon Riggs , Josh Berkus , pgsql-performance@postgresql.org, Alvaro Herrera Subject: Re: User concurrency thresholding: where do I look? In-reply-to: <46A8BD62.2080904@sun.com> References: <200707190828.59088.josh@agliodbs.com> <200707191819.13899.josh@agliodbs.com> <15685.1184895926@sss.pgh.pa.us> <200707192138.39679.josh@agliodbs.com> <46A0FA31.2080208@sun.com> <12002.1184955831@sss.pgh.pa.us> <46A1055F.9010304@sun.com> <12445.1184958793@sss.pgh.pa.us> <46A11116.5030905@sun.com> <14909.1184962561@sss.pgh.pa.us> <46A1205B.8010205@sun.com> <15343.1184965054@sss.pgh.pa.us> <1185180668.4284.149.camel@ebony.site> <23848.1185199901@sss.pgh.pa.us> <1185201556.4284.243.camel@ebony.site> <25095.1185202498@sss.pgh.pa.us> <1185205663.4284.249.camel@ebony.site> <1185212261.4284.270.camel@ebony.site> <1545.1185214760@sss.pgh.pa.us> <46A7D5AD.9000706@sun.com> <13162.1185405865@sss.pgh.pa.us> <46A8AFDF.3050804@sun.com> <26825.1185460816@sss.pgh.pa.us> <46A8BD62.2080904@sun.com> Comments: In-reply-to "Jignesh K. Shah" message dated "Thu, 26 Jul 2007 11:27:30 -0400" Date: Thu, 26 Jul 2007 11:42:48 -0400 Message-ID: <27577.1185464568@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/368 X-Sequence-Number: 26052 "Jignesh K. Shah" writes: > For 600-850 Users: that potential mislabeled CheckPointStartLock or > LockID==12 comes from various sources where the top source (while system > is still doing great) comes from: > postgres`LWLockAcquire+0x1c8 > postgres`SimpleLruReadPage_ReadOnly+0xc > postgres`TransactionIdGetStatus+0x14 That path would be taking CLogControlLock ... so you're off by at least one. Compare the script to src/include/storage/lwlock.h. regards, tom lane