X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E35603A5C0A for ; Wed, 26 Jan 2005 15:17:53 +0000 (GMT) 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 30129-09 for ; Wed, 26 Jan 2005 15:17:46 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7B8B93A5C25 for ; Wed, 26 Jan 2005 15:17:50 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0QFHh0q014871; Wed, 26 Jan 2005 10:17:44 -0500 (EST) To: Hannu Krosing Cc: Simon Riggs , Tatsuo Ishii , marty@outputservices.com, herve@elma.fr, pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering In-reply-to: <1106732479.5587.4.camel@fuji.krosing.net> References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <20050122.121300.41631131.t-ishii@sra.co.jp> <25335.1106428223@sss.pgh.pa.us> <1106511352.31592.112.camel@localhost.localdomain> <6346.1106512803@sss.pgh.pa.us> <1106531786.5790.9.camel@fuji.krosing.net> <3582.1106667713@sss.pgh.pa.us> <1106732479.5587.4.camel@fuji.krosing.net> Comments: In-reply-to Hannu Krosing message dated "Wed, 26 Jan 2005 11:41:18 +0200" Date: Wed, 26 Jan 2005 10:17:43 -0500 Message-ID: <14870.1106752663@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/500 X-Sequence-Number: 10190 Hannu Krosing writes: > But can't clearing up the index be left for "later" ? Based on what? Are you going to store the information about what has to be cleaned up somewhere else, and if so where? > Indexscan has to check the data tuple anyway, at least for visibility. > would adding the check for field sameness in index and data tuples be > too big performance hit ? It does pretty much suck, especially when you think about functional indexes on expensive functions. regards, tom lane