Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 5E06E2E0060 for ; Fri, 2 May 2008 18:44:09 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 77993-07 for ; Fri, 2 May 2008 18:44:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by developer.postgresql.org (Postfix) with ESMTP id 3BF2D2E0080 for ; Fri, 2 May 2008 18:44:06 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Fri, 02 May 2008 16:44:04 -0500 Message-Id: <481B44AF.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Fri, 02 May 2008 16:43:58 -0500 From: "Kevin Grittner" To: "Alexy Khrabrov" , "Greg Smith" Cc: Subject: Re: two memory-consuming postgres processes References: <27A4D379-2553-496D-A96C-102F2A5E62C2@gmail.com> <21403.1209759217@sss.pgh.pa.us> <72E02D29-848B-467A-AE6B-401568010254@gmail.com> <481B8160.2090106@emolecules.com> <1F7A4C3D-C8A3-44BC-A324-E9BA409BB479@gmail.com> In-Reply-To: <1F7A4C3D-C8A3-44BC-A324-E9BA409BB479@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/36 X-Sequence-Number: 30004 >>> Alexy Khrabrov wrote: > SInce I don't index on that > new column, I'd assume my old indices would do -- do they change > because of rows deletions/insertions, with the effective new rows > addresses? Every update is a delete and insert. The new version of the row must be added to the index. Every access through the index then has to look at both versions of the row to see which one is "current" for its transaction. Vacuum will make the space used by the dead rows available for reuse, as well as removing the old index entries and making that space available for new index entries. -Kevin