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 36B4E565AA for ; Mon, 21 Mar 2005 05:13:06 +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 51471-07 for ; Mon, 21 Mar 2005 05:13:00 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by svr1.postgresql.org (Postfix) with ESMTP id 7E07956494 for ; Mon, 21 Mar 2005 05:12:59 +0000 (GMT) Received: from grownups (c-24-21-166-228.client.comcast.net[24.21.166.228]) by comcast.net (rwcrmhc12) with SMTP id <20050321051255014004rjnpe>; Mon, 21 Mar 2005 05:12:59 +0000 Message-ID: <005901c52dd4$e3877830$0200a8c0@grownups> From: "Stacy White" To: "Tom Lane" Cc: "Alvaro Herrera" , "PFC" , "Josh Berkus" , References: <200503191202.38089.josh@agliodbs.com> <20050319225624.GA8467@dcc.uchile.cl> <3404.1111277153@sss.pgh.pa.us> <002a01c52d87$543d1010$0200a8c0@grownups> <14172.1111359709@sss.pgh.pa.us> Subject: Re: What needs to be done for real Partitioning? Date: Sun, 20 Mar 2005 21:14:37 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.259 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200503/412 X-Sequence-Number: 11117 From: "Tom Lane" > "Stacy White" writes: > > FWIW, we see large benefits from partitioning other than the ability to > > easily drop data, for example: > > > - We can vacuum only the active portions of a table > > - Postgres automatically keeps related records clustered together on disk, > > which makes it more likely that the blocks used by common queries can be > > found in cache > > - The query engine uses full table scans on the relevant sections of data, > > and quickly skips over the irrelevant sections > > - 'CLUSTER'ing a single partition is likely to be significantly more > > performant than clustering a large table > Global indexes would seriously reduce the performance of both vacuum and > cluster for a single partition, and if you want seq scans you don't need > an index for that at all. So the above doesn't strike me as a strong > argument for global indexes ... Tom, this list was in response to your question "If you have to do index cleaning before you can drop a partition, what's the point of partitioning?". I was trying to make the point that partioning isn't just about being able to quickly drop data. The argument for global indexes came in the form of my war story and the description of the conditions under which global indexes will perform better than local indexes (see my original email for details) . But, like I said, this would definitely be a phase II/III item.