Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 6C2DD64FC3B for ; Thu, 25 Sep 2008 14:35:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 62653-04 for ; Thu, 25 Sep 2008 14:35:34 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 85F3E64FC01 for ; Thu, 25 Sep 2008 14:35:34 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8PHZT0D009092; Thu, 25 Sep 2008 13:35:29 -0400 (EDT) To: "Aras Angelo" cc: pgsql-admin@postgresql.org Subject: Re: Strange highload on server In-reply-to: <5136d4130809250925s7d5b873ft7c64cb67db5047be@mail.gmail.com> References: <5136d4130809250925s7d5b873ft7c64cb67db5047be@mail.gmail.com> Comments: In-reply-to "Aras Angelo" message dated "Thu, 25 Sep 2008 09:25:33 -0700" Date: Thu, 25 Sep 2008 13:35:29 -0400 Message-ID: <9091.1222364129@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/304 X-Sequence-Number: 30397 "Aras Angelo" writes: > We have been running our database server without any problem or reboot at > all for a year. Yesterday we needed to change servers so we went ahead and > installed the same postgresql version (8.2.1), restored the database files, > ran some tests offline. Everything was good. As soon as we launch the site > and the traffic hits the server, the load is going up to the sky, and the > top command lists nothing but postgres processes. Strangely, even if i kill > Apache and stop the traffic, somehow the load doesnt cool down, so i thought > this might be an issue with postgres processes not timing out or something. > But we use a very minimal config and the same config was being used in our > other server without any problem. I suspect you forgot to re-ANALYZE your tables after reloading all the data. BTW, running a production site on 8.2.1 borders on negligence. You're missing more than a year and a half's worth of bug fixes, including at least one serious risk of data loss. regards, tom lane