X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 85216DB0AC for ; Mon, 21 Nov 2005 19:07:30 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88439-07-4 for ; Mon, 21 Nov 2005 23:07:31 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id 05766DAAA1 for ; Mon, 21 Nov 2005 19:07:17 -0400 (AST) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr2.postgresql.org (Postfix) with ESMTP id 11F76F0D54 for ; Mon, 21 Nov 2005 16:43:59 +0000 (GMT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 21 Nov 2005 10:43:38 -0600 Subject: Re: VERY slow after many updates From: Scott Marlowe To: Alex Wang Cc: Csaba Nagy , postgres performance list In-Reply-To: <006b01c5ed04$f640ef70$0200a8c0@alexxp> References: <002601c5ecdd$503279e0$0200a8c0@alexxp> <1132398732.10890.480.camel@coppola.muc.ecircle.de> <005201c5ed01$7f15c310$0200a8c0@alexxp> <1132402372.10890.487.camel@coppola.muc.ecircle.de> <006b01c5ed04$f640ef70$0200a8c0@alexxp> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1132591417.28788.7.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 21 Nov 2005 10:43:38 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200511/428 X-Sequence-Number: 15685 On Sat, 2005-11-19 at 06:29, Alex Wang wrote: > Great infomation. I didn't know that update is equal to delete+insert in > Postgres. I would be more careful on designing the database access method in > this case. Just make sure you have regular vacuums scheduled (or run them from within your app) and you're fine.