Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id EA33D1337B56 for ; Sat, 4 Dec 2010 17:58:18 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 63148-10 for ; Sat, 4 Dec 2010 21:58:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.123]) by mail.postgresql.org (Postfix) with ESMTP id 6B18A1337B54 for ; Sat, 4 Dec 2010 17:58:11 -0400 (AST) X-Authority-Analysis: v=1.1 cv=6ptpMFIBtxRk0xdOb6IhJTbTLVRlKjWFes7R4SsWCrA= c=1 sm=0 a=NdO16byWu90A:10 a=JRZeEW2aRuwA:10 a=8nJEP1OIZ-IA:10 a=RAii6je2cdnAH6ATCOpc6g==:17 a=_Ixf_7qHAAAA:8 a=nQJ5FtgEob0OSrEMWdUA:9 a=esNdneJBq99bM8WleHkA:7 a=eEQlA9yEtSsBeayoryC0k0cXP_AA:4 a=wPNLvfGTeEIA:10 a=ryAo9hy1-OkA:10 a=6vsjEBoLwlAA:10 a=0tfO7MgyNwYA:10 a=RAii6je2cdnAH6ATCOpc6g==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.73.87.196 Received: from [74.73.87.196] ([74.73.87.196:13870] helo=[192.168.1.100]) by hrndva-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id E6/8E-26142-279BAFC4; Sat, 04 Dec 2010 21:58:10 +0000 Message-ID: <4CFAB972.5050806@vmsinfo.com> Date: Sat, 04 Dec 2010 16:58:10 -0500 From: Mladen Gogala Reply-To: mladen.gogala@vmsinfo.com Organization: VMS User-Agent: Thunderbird 2.0.0.24 (X11/20101126) MIME-Version: 1.0 To: Tom Lane CC: John Papandriopoulos , "pgsql-performance@postgresql.org" Subject: Re: Query-plan for partitioned UPDATE/DELETE slow and swaps vmem compared to SELECT References: <14012.1291443654@sss.pgh.pa.us> <23792.1291480923@sss.pgh.pa.us> In-Reply-To: <23792.1291480923@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201012/44 X-Sequence-Number: 41496 Tom Lane wrote: > Hmm. Rules? Triggers? You seem to be assuming the problem is at the > planner stage but I'm not sure you've proven that. > > regards, tom lane > > Hmmm, I vaguely recollect a similar thread, started by me, although with fewer partitions. In my experience, planner doesn't do a very good job with partitions, especially with things like "min" or "max" which should not be resolved by a full table scan, if there are indexes on partitions. -- Mladen Gogala Sr. Oracle DBA 1500 Broadway New York, NY 10036 (212) 329-5251 www.vmsinfo.com