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 EF206D880E for ; Wed, 31 Aug 2005 02:18:01 -0300 (ADT) 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 99800-07 for ; Wed, 31 Aug 2005 05:17:58 +0000 (GMT) Received: from calypso.bi.lt (calypso.bi.lt [213.226.153.10]) by svr1.postgresql.org (Postfix) with ESMTP id 087BCD8831 for ; Wed, 31 Aug 2005 02:17:54 -0300 (ADT) Received: by calypso.bi.lt (Postfix, from userid 101) id E7E9C48054F; Wed, 31 Aug 2005 08:17:53 +0300 (EEST) X-Original-To: pgsql-performance@postgresql.org Received: from B027543 (inet.bee.lt [213.226.131.30]) by calypso.bi.lt (Postfix) with SMTP id D60F94804CC for ; Wed, 31 Aug 2005 08:17:53 +0300 (EEST) Message-ID: <00f601c5adeb$56fcb910$f20214ac@bite.lt> From: "Mindaugas Riauba" To: References: <4314DBE0.9070708@telogis.com> <200508301558.34697.josh@agliodbs.com> Subject: Re: 'Real' auto vacuum? Date: Wed, 31 Aug 2005 08:17:53 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.09 required=5 tests=[AWL=0.090] X-Spam-Level: X-Archive-Number: 200508/555 X-Sequence-Number: 14302 > > When a row is orphaned it's added to a list of possibly available rows. > > When a new row is needed the list of possible rows is examined and the > > first one with a transaction id less then the lowest running transaction > > id is chosen to be the new row? These rows can be in a heap so it's > > really fast to find one. > > This is the long-term plan. However, it's actually a lot harder than it > sounds. Patches welcome. Some ETA? Since that would be the most welcome addition for us. We have few very heavily updated databases where table bloat and constant vacuuming is killing performance. Mindaugas