Skip site navigation (1) Skip section navigation (2)

Re: plan time of MASSIVE partitioning ...

From: Leonardo Francalanci <m_lists(at)yahoo(dot)it>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plan time of MASSIVE partitioning ...
Date: 2010-10-29 15:41:18
Message-ID: 919158.72344.qm@web29006.mail.ird.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> This is going to be dominated by constraint exclusion  checking.  There's
> basically no fix for that except a more explicit  representation of the
> partitioning rules.  

Damn, I knew that was going to be more complicated :)

So in which case does this patch help? I guess in a multi-index
scenario? childtables.sql is kind of hard to read (I think a FOR loop
would have been more auto-explaining?).


      

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-10-29 15:54:52
Subject: Re: crash in plancache with subtransactions
Previous:From: Alvaro HerreraDate: 2010-10-29 15:40:47
Subject: Re: crash in plancache with subtransactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group