Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id B601C6339B9 for ; Mon, 21 Sep 2009 22:56:19 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 39276-03 for ; Tue, 22 Sep 2009 01:56:00 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-iw0-f204.google.com (mail-iw0-f204.google.com [209.85.223.204]) by mail.postgresql.org (Postfix) with ESMTP id E1440633732 for ; Mon, 21 Sep 2009 22:56:08 -0300 (ADT) Received: by iwn42 with SMTP id 42so1926398iwn.28 for ; Mon, 21 Sep 2009 18:56:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=a5F28pJQ97YEdQMdza0/Pns/GZdEqf9ucJ8P1pme0Hs=; b=mNejvVvLLpikqu/2nGLt4eAXEFcychJPLdeu3OuyjmyEB6uLhRux4dqgTt87c+vQ/y LlUkA4mVq3YoB4apcrMOng74cB7/7Rif254RfUZckuKmnJzX2pWmSxPkfUurHtF3b0z8 Q//QTB7U6RbhcUV5K+sCD4pJ8wKTaQ44L25xU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pKJSxOl1ZVBQDw4E7+qKL3/IVLplkwSGo281Av99NpZoUylZeaYhIEpwzH9+ZSvT1p CcmH106ObmNVEBgQ2RdDCgwX4Z1wF2Kkf5R2RKDnpt0e4J5foaUMIuGi0gkBGXkW+kQg kPYs4b19wQsXWfN6n/kfOXnbCIANzEtUvjs3s= MIME-Version: 1.0 Received: by 10.231.121.95 with SMTP id g31mr731420ibr.24.1253584566935; Mon, 21 Sep 2009 18:56:06 -0700 (PDT) In-Reply-To: <4AB786A0.4040408@lux.com.mx> References: <4AB786A0.4040408@lux.com.mx> Date: Mon, 21 Sep 2009 19:56:06 -0600 Message-ID: Subject: Re: Working slow From: Scott Marlowe To: Judith Altamirano Cc: pgsql-sql@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.483 tagged_above=-10 required=5 tests=AWL=0.116, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200909/98 X-Sequence-Number: 33163 On Mon, Sep 21, 2009 at 7:58 AM, Judith Altamirano wrote: > hello every body, I'm having a data base in a point of sale that is getting > frozen, I already have run a vacuum -z -d to reindex the data base and > nothing happens...... Some suggestions to speed the process, Do you guys > think that the data base is nearly to broke? vacuumdb does not reindex, reindexdb does that. Hard to say with so little evidence. What does top, or vmstat 1, or iostat 10 or select datname, current_query, waiting, (now()-query_start)::time(0) as runtime from pg_stat_Activity where current_query not ilike '%idle%' order by query_start limit 10 have to say? Is the database already bloated? If so, how big is /data/base compared to usual?