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 1D7ED3A5B30 for ; Wed, 26 Jan 2005 09:41:43 +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 93403-03 for ; Wed, 26 Jan 2005 09:41:29 +0000 (GMT) Received: from fuji.krosing.net (joltid-gw.joltid.org [195.50.194.24]) by svr1.postgresql.org (Postfix) with ESMTP id E83033A5B34 for ; Wed, 26 Jan 2005 09:41:29 +0000 (GMT) Received: from fuji.krosing.net (localhost.joltid.net [127.0.0.1]) by fuji.krosing.net (8.13.1/8.13.1) with ESMTP id j0Q9fLvY005868; Wed, 26 Jan 2005 11:41:21 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.13.1/8.13.1/Submit) id j0Q9fJtM005867; Wed, 26 Jan 2005 11:41:19 +0200 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: PostgreSQL clustering VS MySQL clustering From: Hannu Krosing To: Tom Lane Cc: Simon Riggs , Tatsuo Ishii , marty@outputservices.com, herve@elma.fr, pgsql-performance@postgresql.org In-Reply-To: <3582.1106667713@sss.pgh.pa.us> 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> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Jan 2005 11:41:18 +0200 Message-Id: <1106732479.5587.4.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/494 X-Sequence-Number: 10184 =DChel kenal p=E4eval (teisip=E4ev, 25. jaanuar 2005, 10:41-0500), kirjutas Tom Lane: > Hannu Krosing writes: > > Why is removing index entries essential ? >=20 > Because once you re-use the tuple slot, any leftover index entries would > be pointing to the wrong rows. That much I understood ;) But can't clearing up the index be left for "later" ?=20 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 ? > regards, tom lane >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? >=20 > http://www.postgresql.org/docs/faq --=20 Hannu Krosing