X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1D9A4D1C9D8 for ; Tue, 5 Aug 2003 13:33:24 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 10189-02 for ; Tue, 5 Aug 2003 10:32:09 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 4B9F2D1C9C9 for ; Tue, 5 Aug 2003 10:33:12 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h75DXUjg002985 for ; Tue, 5 Aug 2003 19:03:30 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h75DXUip002972 for ; Tue, 5 Aug 2003 19:03:30 +0530 From: "Shridhar Daithankar" To: "pgsql-performance@postgresql.org" Date: Tue, 05 Aug 2003 19:05:05 +0530 MIME-Version: 1.0 Subject: Re: Some vacuum & tuning help Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F2FFFE1.6163.9BBBFB@localhost> In-reply-to: References: <3F2FF1E6.10579.651E89@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/60 X-Sequence-Number: 2877 On 5 Aug 2003 at 9:18, Jeff wrote: > As for the pg_dumping of it. I suppose it would work on this table as it > is only a couple million rows and not terribly big data-wise. The other > tables in this db are rather big and a load is not fast. (It is about > 8GB). You need to dump only those table which has unusualy high unused stats. If that is a small table, dump/reload it would be far faster than vacuum.. For others vacuum analyse should do.. > > You mean linux? I guess you need a kernel revision for a long time. How about > > 2.4.21? > > > Yeah, linux. We're planning on upgrading when we relocate datacenters at > the end of August. This machine has actually been up for 486 days (We're > hoping to reach linux's uptime wraparound of 496 days :) and the only > reason it went down then was because the power supply failed. (That can > be read: pg7.0.2 had over a year of uptime. lets hope 7.3 works as good :) Good to know that. AFAIK, the 496 wraparound is fixed in 2.6. So that won't be a complaint any longer.. Bye Shridhar -- Gravity: What you get when you eat too much and too fast.