Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8F4D6650DBC for ; Mon, 30 Jun 2008 22:05:39 -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 92225-02 for ; Mon, 30 Jun 2008 22:05:17 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by postgresql.org (Postfix) with ESMTP id 70B29650E81 for ; Mon, 30 Jun 2008 22:05:15 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so1891379rvf.43 for ; Mon, 30 Jun 2008 18:05:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=0J1Oi2/T2/bQjmjRbYKd+giDUbb/0Uq1C9CluoRM0G4=; b=ule8XbfZObW6LtFKDIC625XZGmrO00H67pefvGgiPHq5JJh1Sc+BavdmOpMejjzLt2 cWQzvXjUlkKFaJ4BUnTDAu3hIrzEJ/OlYsl0UA4CDbB+CKqfdXUQlfiV0O1Te5FToon/ VqiOzBnIojDTINbXJj5dlneDH7xOoK568BL2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=f9vl78DQ2L+cVLZiPZo5PYGGMg4grbi7A2hQXPqNN3Ff+ECyTA8TcbGvTVEW8wcHMA KksgKuVZ4kzA98zDCljk7hhkbT9lv77tUor2urMHn4H2nl5Qy/2uMJvWGL7077mC+g01 lv9lI75PTQyDwizMHZBvDjBr577L6DnxJNAhk= Received: by 10.114.184.7 with SMTP id h7mr5018334waf.9.1214874310888; Mon, 30 Jun 2008 18:05:10 -0700 (PDT) Received: by 10.114.180.17 with HTTP; Mon, 30 Jun 2008 18:05:10 -0700 (PDT) Message-ID: Date: Mon, 30 Jun 2008 19:05:10 -0600 From: "Scott Marlowe" To: "Rafael Domiciano" Subject: Re: Configuring Shared Buffers Cc: "Alvaro Herrera" , "Tino Schwarze" , pgsql-admin@postgresql.org In-Reply-To: <3a0028490806301712o6a07d77nba5faded7fa4fb98@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3a0028490806301052y193a4aeayfcc6deafdeb1cdb2@mail.gmail.com> <3a0028490806301201m5e4c48d4qc51a880b8f80ecf5@mail.gmail.com> <20080630191710.GC5358@easy2.in-chemnitz.de> <3a0028490806301616v6882a40bi2b54dcf63b37e315@mail.gmail.com> <20080630231940.GE18252@alvh.no-ip.org> <3a0028490806301641y780fdf52o9d6c473a9fe91d88@mail.gmail.com> <20080630234536.GF18252@alvh.no-ip.org> <3a0028490806301651l6f3f58a3y5297ae59272b82f0@mail.gmail.com> <20080630235959.GG18252@alvh.no-ip.org> <3a0028490806301712o6a07d77nba5faded7fa4fb98@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/268 X-Sequence-Number: 29606 Updates =3D delete / insert inserts only create dead tuples if they fail. So, assuming no failed inserts, you're creating 55k dead tuples a day. You can run vacuum verbose to get a report on how many dead tuples your tables / database has to get an idea if you're vacuuming often enough. If vacuuming makes the machine too slow look at setting vacuum_cost_delay =3D 10 and see if that helps. Vacuums will take longer but won't be as intrusive. On Mon, Jun 30, 2008 at 6:12 PM, Rafael Domiciano wrote: > No, but is more common Insert and Update than delete. > While I have around 50.000 Insert and Update, in delete is 5.000 > > 2008/6/30 Alvaro Herrera : >> >> Rafael Domiciano escribi=F3: >> > I have schedelus to run vacuum at the night, it starts at 01:00 AM >> >> Do you execute lots of updates or deletes on some tables? >> >> -- >> Alvaro Herrera >> http://www.CommandPrompt.com/ >> PostgreSQL Replication, Consulting, Custom Development, 24x7 support > >