X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 39BA89FB257 for ; Tue, 29 Aug 2006 12:04:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 90845-07 for ; Tue, 29 Aug 2006 12:03:48 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by postgresql.org (Postfix) with ESMTP id C6E319FB22E for ; Tue, 29 Aug 2006 12:03:40 -0300 (ADT) Received: from fe-amer-03.sun.com ([192.18.108.177]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k7TF3eUx015903 for ; Tue, 29 Aug 2006 09:03:40 -0600 (MDT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J4R00B01LKPD500@mail-amer.sun.com> (original mail from J.K.Shah@Sun.COM) for pgsql-performance@postgresql.org; Tue, 29 Aug 2006 09:03:40 -0600 (MDT) Received: from [129.156.85.92] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J4R00LYLLU3STW6@mail-amer.sun.com>; Tue, 29 Aug 2006 09:03:40 -0600 (MDT) Date: Tue, 29 Aug 2006 16:03:38 +0100 From: "Jignesh K. Shah" Subject: Re: slow i/o In-reply-to: <8d04ce990608281606r153ed796xcf5d9d3a44d8e632@mail.gmail.com> To: Junaili Lie Cc: pgsql-performance@postgresql.org Message-id: <44F4574A.3040705@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <8d04ce990608281606r153ed796xcf5d9d3a44d8e632@mail.gmail.com> User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050322) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200608/456 X-Sequence-Number: 20641 Did you increase the checkpoint segments and changed the default WAL lock method to fdsync? http://blogs.sun.com/jkshah/entry/postgresql_on_solaris_better_use Try fdsync instead of fysnc as mentioned in the entry. Regards, Jignesh Junaili Lie wrote: > Hi everyone, > We have a postgresql 8.1 installed on Solaris 10. It is running fine. > However, for the past couple days, we have seen the i/o reports > indicating that the i/o is busy most of the time. Before this, we only > saw i/o being busy occasionally (very rare). So far, there has been no > performance complaints by customers, and the slow query reports doesn't > indicate anything out of the ordinary. > There's no code changes on the applications layer and no database > configuration changes. > I am wondering if there's a tool out there on Solaris to tell which > process is doing most of the i/o activity? > Thank you in advance. > > J >