X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id AEF33D1E930 for ; Thu, 29 Apr 2004 16:13:12 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 26966-08 for ; Thu, 29 Apr 2004 16:12:53 -0300 (ADT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id 212B7D1E5F7 for ; Thu, 29 Apr 2004 16:12:52 -0300 (ADT) Received: from [134.22.68.249] (dyn-68-249.tor.dsl.tht.net [134.22.68.249]) by tht.net (Postfix) with ESMTP id E5F9276B03; Thu, 29 Apr 2004 15:12:56 -0400 (EDT) Subject: Re: planner/optimizer question From: Rod Taylor To: Gary Doades Cc: Postgresql Performance In-Reply-To: <409153EF.24647.144E9BF7@localhost> References: <27806.1083157504@sss.pgh.pa.us> <409153EF.24647.144E9BF7@localhost> Content-Type: text/plain Message-Id: <1083265934.30065.359.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 29 Apr 2004 15:12:15 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/499 X-Sequence-Number: 6799 > I would be nice to get a feel for how much performance loss would be incurred in > maintaining the index flags against possible performance gains for getting the data back > out again. I guess the real question is, why maintain index flags and not simply drop the index entry altogether? A more interesting case would be to have the backend process record index tuples that it would invalidate (if committed), then on commit send that list to a garbage collection process. It's still vacuum -- just the reaction time for it would be much quicker.