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 8BAFF3A427E for ; Sat, 22 Jan 2005 13:18:31 +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 35786-03 for ; Sat, 22 Jan 2005 13:18:25 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by svr1.postgresql.org (Postfix) with ESMTP id 4961D3A4EA0 for ; Sat, 22 Jan 2005 13:18:27 +0000 (GMT) Received: by rproxy.gmail.com with SMTP id z35so233577rne for ; Sat, 22 Jan 2005 05:18:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=L8N6FC3YmBOUeXMjDeJq9wyzVmDxLyiKOdvBqigoYtBez314unuNq96KH6+vyPNFzS/K/cOEVsLiutWhMoVar0HoyHd8pgTF+K6/NRMnqbZ/Z2mNwFQjJuFIUSM4Z5ok9TGhGOEmar/9KXFbbB+9ihb+A7mcVu/ll1WmVj9T6FI= Received: by 10.38.104.5 with SMTP id b5mr41805rnc; Sat, 22 Jan 2005 05:18:27 -0800 (PST) Received: by 10.38.163.47 with HTTP; Sat, 22 Jan 2005 05:18:27 -0800 (PST) Message-ID: <758d5e7f0501220518477cedfa@mail.gmail.com> Date: Sat, 22 Jan 2005 14:18:27 +0100 From: Dawid Kuroczko Reply-To: Dawid Kuroczko To: pgsql-performance@postgresql.org Subject: PostgreSQL clustering VS MySQL clustering In-Reply-To: <758d5e7f050122011713f9e27f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <20050122.121300.41631131.t-ishii@sra.co.jp> <758d5e7f050122011713f9e27f@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.556 tagged_above=0 required=5 tests=AWL, FROM_ENDS_IN_NUMS, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200501/409 X-Sequence-Number: 10099 On Sat, 22 Jan 2005 12:13:00 +0900 (JST), Tatsuo Ishii wrote: > IMO the bottle neck is not WAL but table/index bloat. Lots of updates > on large tables will produce lots of dead tuples. Problem is, There' > is no effective way to reuse these dead tuples since VACUUM on huge > tables takes longer time. 8.0 adds new vacuum delay > paramters. Unfortunately this does not help. It just make the > execution time of VACUUM longer, that means more and more dead tuples > are being made while updating. > > 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". Quick thought -- would it be to possible to implement a 'partial VACUUM' per analogiam to partial indexes? It would be then posiible to do: VACUUM footable WHERE footime < current_date - 60; after a statement to DELETE all/some rows older than 60 days. The VACUUM would check visibility of columns which are mentioned in an index (in this case: footable_footime_index ;)). Of course it is not a great solution, but could be great for doing housecleaning after large update/delete in a known range. ...and should be relatively simple to implement, I guess (maybe without 'ANALYZE' part). Regards, Dawid