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 B0EC23A4F58 for ; Sat, 22 Jan 2005 21:10:36 +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 02020-03 for ; Sat, 22 Jan 2005 21:10:27 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 669923A4ED0 for ; Sat, 22 Jan 2005 21:10:28 +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 j0MLANjY025336; Sat, 22 Jan 2005 16:10:23 -0500 (EST) To: Tatsuo Ishii Cc: marty@outputservices.com, herve@elma.fr, pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering In-reply-to: <20050122.121300.41631131.t-ishii@sra.co.jp> References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <20050122.121300.41631131.t-ishii@sra.co.jp> Comments: In-reply-to Tatsuo Ishii message dated "Sat, 22 Jan 2005 12:13:00 +0900" Date: Sat, 22 Jan 2005 16:10:23 -0500 Message-ID: <25335.1106428223@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/415 X-Sequence-Number: 10105 Tatsuo Ishii writes: > Probably VACUUM works well for small to medium size tables, but not > for huge ones. I'm considering about to implement "on the spot > salvaging dead tuples". That's impossible on its face, except for the special case where the same transaction inserts and deletes a tuple. In all other cases, the transaction deleting a tuple cannot know whether it will commit. regards, tom lane