Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id AC51B9FB34B for ; Wed, 28 Feb 2007 16:46:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 84866-02 for ; Wed, 28 Feb 2007 16:46:38 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by postgresql.org (Postfix) with ESMTP id 223989FBA37 for ; Wed, 28 Feb 2007 16:46:38 -0400 (AST) Received: from [207.253.108.123] by VL-MH-MR001.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JE600C7PXPNDP60@VL-MH-MR001.ip.videotron.ca> for pgsql-performance@postgresql.org; Wed, 28 Feb 2007 15:46:37 -0500 (EST) Date: Wed, 28 Feb 2007 15:53:32 -0500 From: Carlos Moreno Subject: Re: Upgraded to 8.2.3 --- still having performance issues In-reply-to: <45E5E419.5050804@gmail.com> To: Rodrigo Gonzalez Cc: Carlos Moreno , PostgreSQL Performance Message-id: <45E5EBCC.7090206@mochima.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <45E5B7D2.5020306@mochima.com> <5279.1172683250@sss.pgh.pa.us> <45E5D9D7.5090608@mochima.com> <45E5E419.5050804@gmail.com> User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc4 (X11/20060501) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.592 tagged_above=0 required=5 tests=AWL, BAYES_50, RCVD_IN_NJABL_PROXY, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200702/347 X-Sequence-Number: 23401 Rodrigo Gonzalez wrote: > >> I've since discovered a problem that *may* be related to the >> deterioration >> of the performance *now* --- but that still does not explain the machine >> choking since last night, so any comments or tips are still most >> welcome. >> [...] >> > And the problem that *may* be related is....? > > All the information is required so someone can give you good > information... You are absolutely right, of course --- it was an instance of "making a long story short" for everyone's benefit :-) To make the story as short as possible: I was running a program that does clean up on the database (move records older than 60 days). That program creates log files, and it exhausted the available space on the /home partition (don't ask! :-)). The thing is, all of postgres's data is below the /var partition (which has a total of 200GB, and still around 150GB available) --- in particular, the postgres' home directory is /var/users/postgres, and the database cluster's data directory is /var/users/postgres/data --- that tells me that this issue with the /home partition should not make postgres itself choke; the clean up program was totally choking, of course. And yes, after realizing that, I moved the cleanup program to some place below the /var directory, and /home now has 3.5GB available. Thanks, Carlos --