Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A45F29FB604 for ; Mon, 21 May 2007 17:47:10 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 63271-04 for ; Mon, 21 May 2007 17:47:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 731AB9FB504 for ; Mon, 21 May 2007 17:47:03 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 05B1956495; Mon, 21 May 2007 15:46:59 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 21 May 2007 15:46:55 -0500 Date: Mon, 21 May 2007 15:46:55 -0500 From: "Jim C. Nasby" To: Merlin Moncure Cc: Tarhon-Onu Victor , pgsql-performance@postgresql.org Subject: Re: 500 requests per second Message-ID: <20070521204655.GL62346@nasby.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070521:mmoncure@gmail.com::GM5UQNcJaFicdP3F:0000000000000000000 0000000000000000000000004VPI X-Hashcash: 1:20:070521:mituc@iasi.rdsnet.ro::PslxpXoqrKifK834:00000000000000000 000000000000000000000000Di2/ X-Hashcash: 1:20:070521:pgsql-performance@postgresql.org::XuRlH6dQ2f3CTy12:00000 0000000000000000000000003x+Z X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/401 X-Sequence-Number: 24791 On Mon, May 21, 2007 at 03:50:27PM -0400, Merlin Moncure wrote: > I work on a system about like you describe....400tps constant....24/7. > Major challenges are routine maintenance and locking. Autovacuum is > your friend but you will need to schedule a full vaccum once in a > while because of tps wraparound. If you allow AV to do this, none of > your other tables get vacuumed until it completes....heh! BTW, that's changed in either 8.2 or 8.3; the change is that freeze information is now tracked on a per-table basis instead of per-database. So autovacuum isn't forced into freezing everything in the database at once. -- Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)