Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9C50F9FB4C3 for ; Mon, 21 May 2007 21:52:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 80677-06 for ; Mon, 21 May 2007 21:52:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from beaver.fastcrypt.com (beaver.fastcrypt.com [64.7.141.17]) by postgresql.org (Postfix) with ESMTP id 821CE9FB5A3 for ; Mon, 21 May 2007 21:52:38 -0300 (ADT) Received: from [192.168.1.14] (dcdsl.ebox.com [64.7.143.116]) by beaver.fastcrypt.com (Postfix) with ESMTP id 7906D1580659; Mon, 21 May 2007 21:00:47 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: "Tarhon-Onu Victor" , pgsql-performance@postgresql.org Content-Transfer-Encoding: 7bit From: Dave Cramer Subject: Re: 500 requests per second Date: Mon, 21 May 2007 20:52:43 -0400 To: Merlin Moncure X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/412 X-Sequence-Number: 24802 > * set reasonable statement timeout > * backup with pitr. pg_dump is a headache on extremely busy servers. Where do you put your pitr wal logs so that they don't take up extra I/O ? > * get good i/o system for your box. start with 6 disk raid 10 and go > from there. > * spend some time reading about bgwriter settings, commit_delay, etc. > * keep an eye out for postgresql hot (hopefully coming with 8.3) and > make allowances for it in your design if possible. > * normalize your database and think of vacuum as dangerous enemy. > > good luck! :-) > > merlin > > ---------------------------(end of > broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match