X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9FD653A2D8D for ; Tue, 4 Jan 2005 00:57:45 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13081-02 for ; Tue, 4 Jan 2005 00:57:29 +0000 (GMT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id A82D93A1A18 for ; Tue, 4 Jan 2005 00:57:31 +0000 (GMT) Received: (qmail 29603 invoked from network); 4 Jan 2005 00:57:04 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 4 Jan 2005 00:57:04 -0000 Message-ID: <41D9E9F0.2060905@fastcrypt.com> Date: Mon, 03 Jan 2005 19:57:20 -0500 From: Dave Cramer Reply-To: pg@fastcrypt.com Organization: Postgres International User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amrit@health2.moph.go.th Cc: PGsql-performance Subject: Re: Low Performance for big hospital server .. References: <1104634472.41d762681b548@webmail.moph.go.th> <20050102140828.GA21826@pobox.com> <1104683293.41d8211d62221@webmail.moph.go.th> <41D827C1.3050707@fastcrypt.com> <1104717243.41d8a5bb9cb9b@webmail.moph.go.th> <41D9525D.3000409@fastcrypt.com> <1104766805.41d96755a40d9@webmail.moph.go.th> In-Reply-To: <1104766805.41d96755a40d9@webmail.moph.go.th> Content-Type: text/plain; charset=TIS-620; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.008 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/33 X-Sequence-Number: 9723 amrit@health2.moph.go.th wrote: >>I realize you may be stuck with 7.3.x but you should be aware that 7.4 >>is considerably faster, and 8.0 appears to be even faster yet. >> >> > >There are a little bit incompatibility between 7.3 -8 , so rather difficult to >change. > > > >>I would seriously consider upgrading, if at all possible. >> >>A few more hints. >> >>Random page cost is quite conservative if you have reasonably fast disks. >>Speaking of fast disks, not all disks are created equal, some RAID >>drives are quite slow (Bonnie++ is your friend here) >> >>Sort memory can be set on a per query basis, I'd consider lowering it >>quite low and only increasing it when necessary. >> >>Which brings us to how to find out when it is necessary. >>Turn logging on and turn on log_pid, and log_duration, then you will >>need to sort through the logs to find the slow queries. >> >> > >In standard RH 9.0 , if I enable both of the log [pid , duration] , where could >I look for the result of the log, and would it make the system to be slower? > > On a redhat system logging is more or less disabled if you used the rpm you can set syslog=2 in the postgresql.conf and then you will get the logs in messages.log Yes, it will make it slower, but you have to find out which queries are slow. Dave > >Amrit >Thailand > > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > > > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561