pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: John Papandriopoulos <dr.jpap@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Query-plan for partitioned UPDATE/DELETE slow and swaps vmem compared to SELECT
Date: Sat, 04 Dec 2010 16:58:10 -0500
Message-ID: <4CFAB972.5050806@vmsinfo.com> (raw)
In-Reply-To: <23792.1291480923@sss.pgh.pa.us>
References: <idbo6g$92r$1@news.hub.org>
	<14012.1291443654@sss.pgh.pa.us>
	<idd14l$a4u$1@news.hub.org>
	<23792.1291480923@sss.pgh.pa.us>

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 




view thread (17+ messages)  latest in thread

Message-ID: <4CFAB972.5050806@vmsinfo.com>
Permalink:  ../4CFAB972.5050806@vmsinfo.com/
Also on:    postgresql.org/message-id/4CFAB972.5050806@vmsinfo.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mladen.gogala@vmsinfo.com, tgl@sss.pgh.pa.us, dr.jpap@gmail.com
  Subject: Re: Query-plan for partitioned UPDATE/DELETE slow and swaps vmem compared to SELECT
  In-Reply-To: <4CFAB972.5050806@vmsinfo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox