Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id ADEB02E0049 for ; Wed, 28 Nov 2007 12:15:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 70702-01 for ; Wed, 28 Nov 2007 12:15:23 -0400 (AST) Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 25A192E2D77 for ; Wed, 28 Nov 2007 12:15:23 -0400 (AST) thread-index: Acgx2e7arJWN6FClQYqyOMQOePZY4g== Received: from [172.16.1.57] ([58.65.169.82]) by mail01.enterprisedb.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Nov 2007 11:15:45 -0500 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133 Message-ID: <474D940D.2060005@enterprisedb.com> Date: Wed, 28 Nov 2007 21:15:09 +0500 From: "Usama Munir Dar" User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: "Shadkam Islam" Cc: Subject: Re: Windows XP selects are very slow References: In-Reply-To: Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Nov 2007 16:15:45.0875 (UTC) FILETIME=[EE7AD230:01C831D9] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/356 X-Sequence-Number: 27771 PG generally comes with very basic default settings, one *start* maybe this page for you http://www.webservices.uiuc.edu/postgresql/ Then obviously you will need to work though your query plans and iterate. Shadkam Islam wrote: > Hi All, > > We are having a table whose data we need to bucketize and show. This is > a continuously growing table (archival is a way to trim it to size). > We are facing 2 issues here: > > 1. When the records in the table are in the range of 10K, it works fine > for some time after starting postgres server. But as time passes, the > entire machine becomes slower and slower - to the extent that we need to > go for a restart. Though taskmgr does not show any process consuming > extra-ordinary amount of CPU / Memory. After a restart of postgres > server, things come back to normal. What may be going wrong here? > > 2. When the records cross 200K, the queries (even "select count(*) from > _TABLE_") start taking minutes, and sometimes does not return back at > all. We were previously using MySql and at least this query used to work > OK there. [Our queries are of the form "select sum(col1), sum(col2), > count(col3) ... where .... group by ... " ]. Any suggestions ... > > Below is the tuning parameter changes thet we did with the help from > internet: > > We are starting postgres with the options [-o "-B 4096"], later we added > > a "-S 1024" as well - without any visible improvement. > Machine has 1GB RAM. > > shadkam > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings >